Mar 02 2020
- last edited on
Jan 14 2022
I have configured a built-in policy with an OpenIdConnect provider (which is an Azure AD):
It works fine (I can connect with my account, first time the account is created).
Now, I have created a custom policy also with an OpenIdConnect provider with the exact same parameters (linked to the same Azure AD).
But when I test the custom policy, it creates a new account, it ignores the account already created by the built-in policy. But this is the same Azure AD behind!
What I'd like to achieve is to make the custom policy using the provider created on the Azure Portal.
Do you think this is possible?
Thanks for your help :)
Mar 03 2020 04:34 AMSolution
@SylvainP31Found the answer, I posted it here : https://stackoverflow.com/questions/60494878/how-to-use-a-custom-openid-connect-provider-created-on-...
In short, the issuer was different between the 2 policies (the url metadata was in cause).