This page describes the initial setup steps for using TrustLogin as the source of identity
to perform Identity Provisioning to IBM Verify.

Note: For detailed instructions on operating IBM Verify, please refer to the documentation provided by IBM Verify.

Setup Steps

IBM Verify Settings

1. Log in to IBM Verify with administrator privileges, and click "Security > API Access".

   
   

2. Click "Add API Client".

   
   

3. Enter any name in the "Name" field, and click "Create API Client".

   

4. Click "..." (ellipsis) > "Edit".

   
   

5. Copy the displayed "Client ID" and "Client Secret" to your clipboard.
   Note: The token cannot be viewed again after you "Save". Please make sure you have copied it before proceeding.
   
   
   This completes the preparation on the IBM Verify side. Next, configure the settings on the TrustLogin side.
   

TrustLogin Settings

1. Log in to the TrustLogin Admin Page, and from the "Admin Page > Settings > Optional Features" menu,
   open "Settings" next to "Identity Provisioning".
   
   

2. Click "Add Service".
   
   
3. On the Add Service screen, search for and select "IBM Verify", then click the "Add" button.
   
   
4. You will be redirected to the "Identity Provisioning > IBM Verify" page.
   Click the "Edit" button.
   
   

5. Open "Access Settings", enter the following values for the settings items, and click "Save".

   Tenant Name	Specify the IBM Verify tenant you are using.
   Client ID	The value of "Client ID" you copied in step 5 of IBM Verify Settings
   Client Secret	The value of "Client Secret" you copied in step 5 of IBM Verify Settings

   
   

6. Click the "Connect" button in the upper right of the screen.
   
   

7. Once the button status updates to "Connected", the initial setup is complete.
   
   

Next step: The manual for configuring user synchronization is available here

Values You Can Configure in Attribute Mapping

You can map any attribute on the TrustLogin side to any attribute on the IBM Verify side.
For configuration instructions, see here

Available Default Functions

• default functions common to all services can be specified.