Can you please shed some light to the problems that we are facing. The main problem is that the dynamic configuration service's "Configure" method is never called. How is the structure supposed to work? When we are debugging the login, when is the execution supposed to call the configure method: when the tenant is changes from the login page **or ** when the "Login with Azure AD" -button is clicked? As the configure is called in neither case, what could be the problem here?
OK, thanks!
Thanks, we will try to implement this. How the "AddOpenIdConnect" part should go in this case, where the configuration is defined dynamically? Here is a general example how that normally goes.
context.Services.AddAuthentication()
.AddOpenIdConnect("ABP2AzureADScheme", "Logon with Azure AD", options =>
{
options.Authority = configuration["AzureAd:Instance"] + configuration["AzureAd:TenantId"] + "/v2.0/";
options.ClientId = configuration["AzureAd:ClientId"];
options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
options.CallbackPath = configuration["AzureAd:CallbackPath"];
options.ClientSecret = configuration["AzureAd:ClientSecret"];
options.RequireHttpsMetadata = false;
options.SaveTokens = true;
options.GetClaimsFromUserInfoEndpoint = true;
options.Scope.Add("email");
options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
});
Thanks for the answer! We are aiming to enable Microsoft Entra Id SSO login for some of our customers, that use our (Abp) application. How is that going to work when we cannot configure the azure tenant in the tenant's external login provider configuration? If only the client id and the secret are configurable, how can the customer point the configuration to their Microsoft Entra Id?
Hi alper, thank you for the answer. There is a difference whether a service is down once every couple of years or once every couple of months. Anyway, I had forgotten about the local nuget cache. Of course we can use that as the source and push the packages to our Azure Artifacts feed. Thanks for the tip!
It turns out that abp has made custom nuget package source(some bicycle), which works like a xmas tree. Not a first time and not a last one when it's down, I assume. If you use a azure devops I would highly recommend to enable custom artifact feed. It has built-in capabilities to Azure devops and forward restores to it.
You cannot use custom feed for nuget packages in Azure Artifacts. That's why I suggested a method to enable package loading from the abp nuget server. If this was possible, we could download the packages and push them to Azure Artifacts feed (or where ever). Seems like MS is not going to implement the custom nuget feed capability any time soon.
This happens from time to time (too often I would say) and interferes with our deployments when it happens. This would mitigate the problem so we could cache the packages. https://support.abp.io/QA/Questions/5549/A-way-to-list-all-nuget-packages-from-Abp-nuget-server
Still not clear enough for me, sorry :) Can we "override the default UI to show the displayname instead of name" , without downloading and customising the source code.
Please clarify how. Do you mean adding the DisplayName as extra property? Will the display name already by visible in the UI or do we still need to create the custom page?
Ok, how about customizing the roles page so it would use the normalised name as localisation key. Then in that tenant, the role names could be visualised in a different language. Is this something we could easily do by just replacing the one page or do we need to pull the whole identity pro module to our sources?
