Use the System for Cross-domain Identity Management (SCIM) protocol to synchronize Alibaba Cloud IDaaS accounts to Resource Access Management (RAM) and automate identity management.
Prerequisites
Your Alibaba Cloud account or RAM user has the permissions to create OAuth applications.
Your Alibaba Cloud account or RAM user has the permissions to grant authorization to a ServerApp, and you can grant authorization only to a ServerApp that belongs to your account.
Step 1: Create an OAuth application and grant authorization in the RAM console
Use your Alibaba Cloud account to log on to the RAM console.
In the left-side navigation pane, choose .
Enter the Application Name and Display Name. For the application type, select Server Application, and then click Create Application. The application is created.
Access Token Validity Period defaults to
3600seconds. Valid values: 900 to 10800 seconds.Click the name of the application that you created. On the OAuth Scope tab, click Add OAuth Scopes. In the Add OAuth Scopes dialog box that appears, select /acs/scim, and then click OK.
Set Access Token Validity Period to
3600seconds (valid values: 900 to 10800 seconds).Grant authorization to the OAuth application. On the Application OAuth Scopes tab, click Authorize. On the application authorization page that appears, select Alibaba Cloud Cross-Domain Identity Management, and then click Authorize.
On the App Secrets tab, click Create Secret. The system automatically generates an application key pair that includes an AppSecretId and an AppSecretValue.
After the key is generated, click Download Secret to save the key file to a secure location. After you confirm that the file is saved, click close to exit the current window.
ImportantThe secret is displayed only when it is created. After you close the window, you cannot retrieve it.
Step 2: Configure SCIM synchronization in IDaaS
In the IDaaS instance console, on the Applications page, click Add Application to open the Marketplace, select the Alibaba Cloud User SSO application template, and then add it.
Click the Account Sync tab. Set the synchronization scope, and then click Save.
Turn on Synchronize IDaaS Account on Application.
Configure the basic settings.
Enter
client_idandclient_secret.Log on to the RAM console. In the left-side navigation pane, choose .
Find the application that you want to use for SCIM synchronization and click its name to open the details page.
In the Basic Information section of the application details page, you can get the Application ID (that is, the client_id).
In the secret generation step in Step 1, use AppSecretValue as the Client Secret.
Operation invocation: You can subscribe to specific change events, such as user creation, updates, and deletions. When a related change occurs in IDaaS, the system automatically triggers synchronization and pushes the changes to the target application in real time.
Full push scope: If you select this option, a one-click push sends the data within the scope to the application.
Field mapping: You can customize the SCIM field mappings and adjust the attribute matching rules based on your business requirements. After you make the adjustments, click Save to ensure accurate data synchronization.
ImportantWhen you use the SCIM protocol to synchronize IDaaS accounts to RAM, the mobile phone number and email attributes of users cannot be mapped.
After you complete the configuration, click Save. (Recommended) Use the Test Connectivity feature to check whether the configuration is correct.
If needed, you can use the one-click push feature to push all accounts within the synchronization scope to RAM at once.
Step 3: Synchronize accounts in IDaaS
After you click Push Now, the accounts within the synchronization scope are synchronized to RAM.
When you click Push Now, a green notification appears in the upper-right corner of the page: "The import task is created. To view the task progress, go to Logs - Sync Logs - Task In Progress." You can click View to go to the synchronization log page.
References
If a RAM account fails to be deleted during synchronization, see What do I do if IDaaS fails to synchronize the deletion of a RAM user?