Issues Concerning Connection of App to Azure Active Directory (AD)
Last Updated:
Overview
A client application has been deployed within a tenant. A new requirement is that a 'downstream' customer wishes to use Single Sign On (SSO) to login to the app using their Azure AD.
Applies To
- SSO
- Azure Active Directory
Cause
Solution
Connect the App to Azure AD
For a 'downstream' customer to be able to login using Azure AD SSO, it is necessary to register the app with the instance of Azure AD that belongs to that particular customer. In this way, users who are registered with that Azure AD instance can log in with that connection. For further information, refer to Register your app with Azure AD.
Sync User Profiles
Yes, it is possible to sync the user profiles of the 'downstream' customer to an Auth0 user profile
To enable this feature, select the option 'Sync user profile attributes at each login' option in the Azure AD connection setting.
When enabled, Auth0 automatically syncs user profile data with each user login, thereby ensuring that changes made in the connection source are automatically updated in Auth0.
For further information, refer to Create an Enterprise Connection in Auth0.
Configure Connection to use Certificates
Microsoft does indeed recommend the use of public key certificates to protect against unauthorized access to production applications. For further information, refer to the Microsoft document Register an Application with the Microsoft Identity Platform.
However, Auth0 only supports the use of client secrets at this point. A feature request has been recorded in the Product backlog, but at the time of this writing ( February 2024 ), there is no clear release date.
Related References
- Choose a Connection Type for Azure AD
- Connect your Native App to Azure AD
- User Profile Structure
- Microsoft: User profile attributes