Since you are already logged in as an administrator, a notification Successfully granted admin consent for the requested permissions. Refer to Microsoft's documentation for more information on the difference between Delegated and Application permissions, as well as reference material for each permission. The following permissions are needed if you plan to use the provisioning feature.Īzure updates the permissions for your app however, you still need to provide admin consent. Permissions (from least to most privileged) If you are using CyberArk Identity just for SSO, you only need one of the following permissions. Scroll down the permissions list and select the following permissions, then click Add permissions. Go to API permissions, then click Add a permission. Step 3: Grant the necessary API permissions to your newly registered app. The client secret value will be unavailable once you logout, so it's critical to capture the value now. Go to Certificates & secrets, then click New client secret.Įnter a description and select an expiration date option, then click Add.Ĭopy the client secret value and paste it into a text editor for later use. Step 2: Add Certificates & secrets to allow access to the resource server. The overview page for your registered app appears. Select Accounts in this organizational directory only. Go to App registrations, then click New registration. Log in to your Azure account as an administrator. In addition, each registered application should have the minimum set of API permissions required to perform its function.
For example, if you are adding Azure Active Directory as a directory source in CyberArk Identity in addition to integrating Office 365 for SSO and provisioning, you would register two Azure applications - one for each task. CyberArk recommends registering a new Azure application that is specific to its intended purpose.
0 kommentar(er)
