Importing users from External Sources
Overview
How to Import users From an external data source into Swivel.
Prerequisites
Swivel 3.x initially configured with an internal data source and store see How to initially configure PINsafe
External Data source (AD, ADAM, LDAP, SQL)
Configuration
Create an external data source repository by selecting in the Swivel Administration Console Repository, then Servers. Enter a unique name for the repository Name, and then select Repository Type from the drop down menu, selecting Active or Simple LDAP. Click Apply, and a new data source will appear with the unique name given to it. One XML data source may be created, but multiple AD, LDAP or other data sources may be created.
Select the new data source from under Repository and configure the required parameters.
For more information on configuring the Data Sources see the following sections:
SQL as a data source How To Guide
The next step is to ensure that the transport groups have been set up so that users recive security strings and other information such as PIN numbers.
Configure the Transport Attribute and the settings in Transport Configuration
The next step is to tell Swivel what permissions which groups of users on the Data Source have. On the Swivel administration console select Repository/Groups. The group name is listed at the top, and below this are listed the data sources, defined by their unique names given above. Enter the LDAP path name to a group of users, this needs to be a group/Container and cannot directly be an OU.
Hint: for Swivel 3.6 or later, use the built in LDAP browser, for earler versions, use a LDAP browser.
The next step is to import users into the Swivel store. From the Swivel Administration console select the User Administration and then the required data source, and click on User Sync. This will occur automatic if a periodic synchronisation has been configured for that data source (recommended). Users will appear in the Swivel User Administration page. If no users appear, then check the system logs.
Typical issues with user import include:
Incorrect LDAP pathname
Incorrect username
Network connectivity (firewalls, IP configuration)
AD User has not replicated
