- ABP Framework version: v8.3RC
- UI Type: Blazor WASM
- Database System: EF Core PostgreSQL
- Tiered (for MVC) or Auth Server Separated (for Angular): yes
- Exception message and full stack trace:
- Steps to reproduce the issue:
Hi,
We are upgrading to v8.3-preview with one of the goals being to enable tenants and their users (our implementation is SaaS), to setup user authentication using their entra verification so the tenants can choose to have one authentication.
I read https://abp.io/support/questions/7501/Problems-with-integration-of-Entra-External-ID and noted that this was acknowledged as a bug and would be fixed in next reelase. Before we go down the path of trying to use Entra/SAML can you confirm that this is all working?
There a rea bunch of old articles, support tickets and the sample on Github is now 4 years old, so is there a worked example/screen shots of steps to setup on both the Entra and also on ABP.io project side for each tenant to implement Entra authenticated login?
Thanks, Andrew
1 Answer(s)
-
0
hi
I had confirmed that this is a problem with the customer code.
https://abp.io/support/questions/7501/Problems-with-integration-of-Entra-External-ID#answer-3a13ef86-3957-c408-5840-b3c46c9d87a5
Please add this code to your solution
context.Services.AddOptions<OpenIdConnectOptions>(OpenIdConnectDefaults.AuthenticationScheme) .PostConfigure(options => { options.SignInScheme = IdentityConstants.ExternalScheme; });
