Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
we have a customer that would like to move SSO from Qlik Sense Enterprise and Azure ADFS with Saml to Azure AD B2C with OIDC. We had an issue during the token request because QS sent the parameters inserted correctly in the virtual proxy, like client_id and client_secret that also are compulsory in the virtual proxy definition but the authentication process fail because for Azure, Qlik Sense is "a Native App (public client) and the client_secret cannot be securely stored, therefore not used on this flow". Indeed if we comment the client_secret in the manual process described here:
we can continuous the process and we receive the information in the "id_token" and inserted in the jwt.io we have the correct value.
Here the Microsoft document that explain the parameters to use:
https://learn.microsoft.com/en-us/azure/active-directory-b2c/authorization-code-flow#2-get-an-access...https://learn.microsoft.com/en-us/azure/active-directory-b2c/openid-connect
I would like to know if someone found the correct settings in Azure B2C to permit authentication OIDC with Qlik Sense
Best Regards Thanks
Could you find the solution? I have the same problem.