Importing User Data from External Sources

This topic describes how to create user records in the Genesys configuration that are required when using a RADIUS or LDAP external authentication system.

Introduction

To authenticate a user in a Genesys program using one of the external authentication systems (RADIUS or LDAP), create in the Genesys configuration a user record that matches a record in the external authentication system.

When you create the user record, you must specify these three properties: User name, Employee ID, and External User ID. Mandatory User Record Properties describes these properties.

Mandatory User Record Properties

Property	Description
User name	Corresponds to name in the XML schema. This property is the user's Genesys logon ID, and it uniquely identifies the user in the Genesys configuration. It must be unique across the entire configuration. For a RADIUS server, this property corresponds to the user name in the RADIUS system.
Employee ID	Corresponds to employeeID in the XML schema. This numeric user ID is assigned by the user's company. This ID does not participate in authentication, but is still required by Configuration Server.
External User ID	Corresponds to externalID in the XML schema. Required by LDAP configuration only. Configuration Server uses this ID to match a record in the Genesys configuration with a record in the LDAP directory server. Specifically, Configuration Server substitutes an X symbol in the LDAP URL filter with the value of this property. The filter is part 6 of the LDAP URL; see ldap-url. Therefore, if the filter in the LDAP URL is (mail=X ), then the External User ID property in Genesys configuration represents the mail attribute of the user record in LDAP server.

Creating a User Record in the Genesys Configuration

This section describes three suggested methods to create a user record in your Genesys configuration:

Manual Entry using Genesys Administrator

Use Genesys Administrator to create user records manually, one by one. To do this, create a Person object under one of the folders designated to store Persons information. There is no bulk process available. Be certain to populate all three mandatory fields.

Import an XML data file using Configuration Import Wizard

Create an XML file containing the user records and then import it using the Configuration Import Wizard (CIW). With this method, you can add several user records to Configuration Server in a single stroke. Use the CIW Import Agent Data and then Raw XML Data modes to import. You may create either the CfgAgent object (ordinary Call Center operator), or the CfgPerson object (Administrator).

The XML file can also contain records which update or remove user information from Configuration Server. See Sample XML Data File.

Import XML Data using the Genesys Configuration SDK

Use the Genesys Configuration SDK to create custom programs which write user information to Configuration Server in XML format.

These custom programs can be written in Java, Visual Basic script or JavaScript. They can monitor changes to the user information on the LDAP directory server, then transform those changes to the format described in the latest version of the Configuration SDK Web Services API Reference, and write them directly to Configuration Server.

Sample XML Data File

This sample XML data file contains the three properties that are required by external authentication:

 

<CfgData mode="mt" xmlns="http://www.genesyslab.com/cs">
 
<CfgReference>
<CfgProviderTenantRef id="Environment" name="Environment"/>
<CfgAgentRef id=”AgentToUpdate” name=”smith”/>
</CfgReference>
 
<CfgCreate>
<CfgAgent
id="Betty"
firstName="Betty"
lastName="Smith"
employeeID="00001"
name="bettys"
ownerDBID="Environment"
emailAddress="bettys@company.com"
externalID="bettys@company.com"/>
</CfgCreate>
 
<CfgUpdate>
<CfgAgentUpdate id=”UpdateAgent” DBIDref=”AgentToUpdate” externalID=newmail@Company.com/>
</CfgUpdate>
 
<CfgRemove>
<CfgAgentRef id=”AgentToRemove” name=”Johnson”/>
</CfgRemove>
 
</CfgData>

You could use this data to import user information into the Genesys Database with either the Configuration Import Wizard or the Genesys Configuration SDK.