Closed tejaswigattu closed 2 years ago
This organization is not maintained anymore besides critical security bugfixes (if feasible). This organization will be archived when .NET Core 3.1 end of support is reached (3rd Dec 2022). All new development is happening in the new Duende Software organization.
The new Duende IdentityServer comes with a commercial license but is free for dev/testing/personal projects and companies or individuals making less than 1M USD gross annnual revenue. Please get in touch with us if you have any question.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Questions are community supported only and the authors/maintainers may or may not have time to reply. If you or your company would like commercial support, please see here for more information.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
We are using Identity Server4 has two external login schemes(Azure Ad B2C and Azure AD).
App1 -- has access to login with B2C App2 -- has access to login with Azure AD
If the user is login to App1. when he tries to open the App2 it is directly opening the application without asking for Azure AD login. Ideally this should not happen.
I guess this is due to user is able to login to Azure AD with the same cookie of B2C.
We want to restrict this since few users of B2C not access to Azure AD tenant. Please provide suggestion.