Our solution uses Azure AD for user authentication and is using the following code:
`
AddOpenIdConnect("AzureOpenId", "SSO", 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");
});
When this process registers the user, I would like to fill in the rest of the AbpUsers details (Firstname, Lastname etc). Do I need to override the ExternalUserRegistration code or can it be achieved through configuration of the scopes?
I have a requirement to resolve each tenant by a custom URL. I followed the blog post here https://blog.antosubash.com/posts/abp-extend-tenant-with-custom-host to add a custom field to y tenant table called "Host". When a user navigates to my solution on the URL, it will resolve the tenant automatically. I had a solution based on v4.4 which worked perfectly using this approach as documented in the blog. I upgraded the solution to v6 and the error being returned now is
Translation of 'EF.Property(EntityShaperExpression: Volo.Saas.Tenants.Tenant ValueBufferExpression: ProjectionBindingExpression: EmptyProjectionMember IsNullable: False , "Host")' failed. Either the query source is not an entity type, or the specified property does not exist on the entity type.
I then created a brand new v6.0.0 ABP solution and followed the blog thinking that I perhaps broke something in the upgrade. Unfortunately, it displays the same error.
The code fails as it is unable to find the new custom field added to the entity.
We are developing a brand new tiered web solution (MVC Razor Pages) for one of our clients. The client requirement is to use either OKTA or Salesforce Identity for authentication. Is it possible to remove the IdentityServer component from the tiered solution and replace it with OKTA / SalesForce identity by changing the auth server URLS in the Web and API layer?
I have been working on a solution which is using ABP Framework Version 4.2.0 for a few months now.
ABP Suite works great to generate entities and to update existing entities. I updated an entity this morning with no issue.
I saw that there was an update to the CLI and the Suite and I updated both after I updated my entity this morning.
While working on another ticket, I needed to update another entity but am now receiving this error:
I attempted to uninstall both the suite and the CLI and reinstall, but this did not help.
Any suggestions on getting around this issue?
ABP Framework version: v4.0.2 **UI type: **MVC **DB provider: **EF Core Tiered (MVC) or Identity Server Seperated (Angular): yes
I have a dashboard in my solution which has a number of sections which all load asynchronously. Some of the processes load slower than others. My UI has a bunch of buttons across the top which control the bottom half of the screen. I would like to disable all actions on the screen until all the various asynchronous processes complete. At the moment, when clicking around quickly and not waiting until all sections have completed their load, we receive a javascript error.
ABP Framework version: v4.0.2 UI type: MVC DB provider: EF Core Tiered (MVC) or Identity Server Seperated (Angular): yes
I have a multi tenanted tiered solution (MVC) with a requirement to customise the workflow for both my Web Solution and the react mobile application. My solution has multiple roles per tenant and I need to disable logon for certain roles from both web and mobile.
e.g:
Doctor Role: Only Web Access Patient Role: Only Mobile Access
I also have a requirement to completely restyle the Identoty Server logon. My question is, would i prevent the different role logon inside the identity server or allow the logon and redirect and display an unauthorised page inside the web portal? Would it be better to prevent the logon inside the identity server?
Is there a simple config setting in identoty server to say prevent logon for certain roles?
I have a tiered solution which createds 3 separate docker images
I have them running on 3 seperate VMs hosted behind an NGINX reverse proxy (4 VMs in total). My domain name points to the nginx server, which routes them 4 subdomains to their various components.
The reverse proxy forces SSL infront of the proxy, but communicates over port 80 to the various site components. Both the Identity Server and API work perfectly and are able to login correctly and return data, but the website fails when I click the login button.
Initially it had compolained about an obscure microsoft issue relating to enforcing the scheme to be https for each request. I added the code as suggested by microsoft but it is still failing somewhere in the pipeline. Any ideas?
I have been looking through the Dahsboard sample solution and would like to change out the ChartJs version for AmCharts as we have the required chart license. I have created a widgets according to the docs and I have included reference to the AMCharts CDN in the cshtml file.
Tracing through the code, I can see the div is being found in the JS. I can debug through the code and see the data is being returned correctly (console.log), but the chart is just not rendering in the UI. I created the chart offline in an HTML file and it works, I also added the chart code into a seperate razor page and it works there too, it is just not working when embedded in the widget.
Any help would be appreciated. I have a feeling it is related to the fact that the amcharts JS files are not local?