<< <%SKIN-STRTRANS-SYNCTOC%> >> Setup Object Mapping |
By the end of this section, AD-Plugin settings will be configured and we will be just a click away to run our first sync.
•Login to GSMS portal using valid login credentials.
•Navigate to Company Setup > Customer Information > Company Information.
•Switch to Directory Sync tab and below screen would appear:
•Click on Edit button to update the Sync settings at customer level :
•Enter fields as described below:
Parameter |
Description |
---|---|
Configuration |
Select a preconfigured sync-setting from dropdown. Note that the dropdown will display none if Admin has not setup Synchronization summary as explained in Admin Sync Settings. |
Source ID |
Unique identifier of the source system that relates to its synced customer. |
Sync Person as |
Select either of the two options from dropdown:
•Contacts - Selection of 'Contacts Only’ will result in the system only creating the AD persons as 'Contacts' under the relevant 'customer/sub-customer.
•User & Contacts - Selection of 'Users and Contacts' will result in the system creating users under the relevant customer/sub-customer.
|
Create User Password |
Tick this check-box to create a password to access AT&T GSMS for every newly created user.
Note: Not all users may be required to access GSMS. |
Create Sub-customer Password |
Tick this check-box to create a password to access GSMS for every newly created user in all sub-customers.
Note: You may wish users in one organizational unit access to GSMS but subsequent sub-customer may not require this access. |
Object Class Map |
|
Object Class |
All Mandatory |
User |
Specifies objectClass attribute’s value in the source data that maps to a user. |
Customer |
Specifies objectClass attribute’s value in the source data that maps to a customer. |
Customer Field Map |
|
Customer Field |
All Mandatory |
Name |
Read-only, Specifies the name of attribute in the source data that maps to sub-customer’s name. |
Source ID |
Read-only, Specifies the name of attribute in the source data that maps to sub-customer’s unique source ID. |
User Field Map |
|
User Field |
All Mandatory |
Source ID |
Specifies the name of attribute in the source data that maps to user’s unique source ID. |
Specifies the name of attribute in the source data that maps to user’s email. |
|
First Name |
Specifies the name of attribute in the source data that maps to user’s First Name. |
Last Name |
Specifies the name of attribute in the source data that maps to user’s Last Name. |
Mobile |
Specifies the name of attribute in the source data that maps to user’s mobile. |
Country |
Specifies the name of attribute in the source data that maps to user’s Country. |
Once you have filled in the above fields, Directory Sync settings for users will appear similar to the below screen:
Important Notes:
•Customer Mapping values must be the attribute within AD to map to the name in GSMS Customer. Administrators must ensure that the name is accurate.
•Customer names must be unique across GSMS. The LDAP (Active Directory) Plug-in sync procedure will ensure this is the case automatically by providing customer names resembling the directory structure in AD.
•Customer Synchronisation Source Id Attribute will always be ‘dn’ and is read-only. Customer Name Attribute will always be ‘ou’ and is read-only.
•User Mapping values must be the attribute within Active Directory to map to the name in AT&T GSMS User field. Administrators must ensure that the name is accurate.