Login to the Curity Admin Web Service and browse to the Token Service Profile
Select Clients from the left navigation pane and create a New Client
Enter a new Client ID and select Ok
Add a ‘Capability’ to your new Client to support Client Credentials
Select the ‘secret’ authentication method and generate a secure Client Secret
Within ‘Scope and Claims’ select the read scope, or some other predefined scope that can read all necessary user attributes from your Curity instance
Apply your Changes by selecting ‘Commit’
From the left navigation menu, select Endpoints from within Token Service and take note of the oauth-token endpoint path (in the default case /oauth/v2/oauth-token)
From the left navigation menu, select Endpoints from within User Management and take note of the um-api endpoint path (in the below case /um/admin)
Finally, from the Curity Admin Web Service, browse to System settings and note the Base URL for the Curity Service
Login to the SGNL Console
From the left menu, select Systems of Record
Add a New System of Record and select Curity
Enter the following data into SGNL:
Once configured, click Continue to save your System of Record and move on to configuring Entities
From the Entities tab, click on ‘Edit Attributes’ to select the entities and attributes you will need synchronized into SGNL to be used in your specified SGNL policies
(If applicable) If you will be synchronizing entities and attributes from 2+ different Systems of Record into SGNL to define policies, click on Add join rule to specify the attribute(s) that will join the entities you’ve configured to synchronize from Curity to other entities in the SGNL Graph
Save the Configuration