When integrating ControlUp with Microsoft Entra ID, two primary authorization methods are available: OAuth and Application Registration. Each method offers distinct functionalities and configurations, catering to different organizational requirements.
*OAuth Integration*
OAuth enables users to authenticate into ControlUp using their Entra ID credentials. This method requires setting up a Service Principal (Enterprise Application) within the Entra ID tenant. Administrators can manage this Service Principal, including restricting user access or revoking consent, independently of the global App Registration. The necessary permission for OAuth is `User.Read`, which allows ControlUp to read basic user attributes such as name and email address. However, OAuth does not inherently support automatic role assignments based on Entra ID group memberships. To achieve such functionality, an additional App Registration is required. ([support.controlup.com](https://support.controlup.com/docs/how-to-set-up-oauth-with-entra-id?utm_source=openai))
*Application Registration Integration*
The Application Registration method involves registering an application within Entra ID and granting it specific permissions to interact with ControlUp. This approach is essential for features like automatic role assignments based on Entra ID group memberships. The required permissions include `User.Read.All`, `Group.Read.All`, `Application.ReadWrite.All` (necessary for automatic SAML setup), and `Policy.ReadWrite.ApplicationConfiguration` (also required for automatic SAML setup). After adding these permissions, administrators must grant admin consent for the application to function correctly. ([support.controlup.com](https://support.controlup.com/v1/docs/microsoft-entra-id-integration?utm_source=openai))
*User Identification in ControlUp*
ControlUp identifies users based on their User Principal Name (UPN), which is typically their work email address. On Windows devices, ControlUp uses the account the user signed in with. On macOS, since there’s no single sign-in UPN, ControlUp looks for a work email address in accounts signed in on the Mac. If ControlUp cannot identify the employee using a device, the device doesn’t appear in any Employees dashboard and doesn’t receive an Experience Score, though it still appears in the Devices view. ([support.controlup.com](https://support.controlup.com/docs/employee-identification?utm_source=openai))
*Conclusion*
For organizations aiming to utilize OAuth with User Delegation in ControlUp, it’s crucial to understand that while OAuth facilitates user authentication, it does not automatically assign roles based on Entra ID group memberships. To achieve this functionality, setting up an Application Registration with the appropriate permissions is necessary. Additionally, ControlUp identifies users based on their UPN, which is typically their work email address.
Read the entire ‘Understanding OAuth and Application Registration in ControlUp’s Entra ID Integration’ thread below:
Can someone explain the difference between the OAuth and Application Registration options in the Entra ID integration?
My goal is straightforward: I want to use OAuth with User Delegation, not SAML or Application Delegation.
The problem is that OAuth does not seem to work as expected. Users are not receiving the permissions associated with their IdP groups.
Is this functionality supposed to work with OAuth and User Delegation, or are these options intended only for automated SAML configuration?
And is it true that ControlUp uses the mail attribute as username instead of the userprincipalname?
Have fix this by the App Registration option. OIDC/OAuth is working fine.
My last question still stands; is it true that CU matches the user based on mail instead of UPN? SAML makes use of UPN.
Continue reading and comment on the thread ‘Understanding OAuth and Application Registration in ControlUp's Entra ID Integration’. Not a member? Join Here!
Categories: All Archives, ControlUp Dashboards
