Sample Kerberos Configuration
Contents
This topic contains examples of how to configure Kerberos for integration with an MIT Key Distribution Center implementation, and for a Microsoft Active Directory implementation.
MIT Key Distribution Center
This section contains a sample configuration to integrate with an MIT Key Distribution Center (KDC) implementation.
Basic Information
KDC installed at: rh5qa64-1.genesyslab.com
Realm: KRBTEST.GENESYSLAB.COM
Sample service name: genesys_sample
Username (known by KDC): testclient with password 123456
On cfglib Client Machine, MIT Client Configuration
File C:\WINDOWS\ krb5.ini, section [realms]:
KRBTEST.GENESYSLAB.COM = {
kdc = rh5qa64-1.genesyslab.com:88
admin_server = rh5qa64-1.genesyslab.com:749
}
On Configuration Server (Server Level):
[authentication]
library=gauth_ldap
...
[gauth_kerberos]
SPN=genesys_sample/rh5qa64-1
realm=KRBTEST.GENESYSLAB.COM
kdc_host=rh5qa64-1.genesyslab.com
...
Person object with username and external ID testclient under the Environment tenant.
Microsoft Active Directory
This section contains a sample configuration to integrate with a Microsoft Active Directory implementation.
Basic Information
Windows domain controller is being used as KDC:
Domain rootDomain.contoso.com
Controller machine: W2k8r-ay-root.rootDomain.contoso.com (135.225.51.14)
Realm: ROOTDOMAIN.CONTOSO.COM
Sample Service name: confserver/somehost
- there is a mapping made from this service name to the windows domain account rootUser2 with password genesys to produce a keytab file with a secret password that can be used on the Configuration Server side.
User name (known by KDC): rootUser1 with password genesys
On cfglib Client Machine, MIT Client Configuration:
File C:\WINDOWS\ krb5.ini, section [realms]
ROOTDOMAIN.CONTOSO.COM = {
kdc = 135.225.51.144
admin_server = 135.225.51.144
}
On Configuration Server (Server Level):
[authentication]
library=gauth_ldap
...
[gauth_kerberos]
SPN=confserver/somehost
realm=ROOTDOMAIN.CONTOSO.COM
kdc_host=135.225.51.144
...
Person object with username and external ID rootUser1 under Environment tenant.
Related Documentation Resources
The following resources provide additional information that is relevant to this software. Consult these additional resources as necessary.
Genesys Framework
Framework 8.5 Deployment Guide,which helps you understand the Genesys Framework architecture, and install and configure the Genesys Framework components.
Framework 8.1 Genesys Administrator Help, which helps you configure and create any necessary configuration objects in Genesys Administrator.
Framework 8.5 Configuration Options Reference Manual, which provides you with the configuration option descriptions for Configuration Server and other Framework components.
Genesys 8.1 Security Deployment Guide, which helps you understand Genesys security and permissions schema.
Genesys
Genesys Licensing Guide, which introduces you to the concepts, terminology, and procedures that are relevant to the Genesys licensing system.
Information about supported hardware and third-party software is available on the Genesys Documentation website in the following documents:
Genesys Supported Operating Environment Reference Guide
Genesys Supported Media Interfaces Reference Guide
For additional system-wide planning tools and information, see the release-specific listings of System Level Documents on the Genesys Documentation website.
Genesys product documentation is available on the:
- Genesys Customer Care website at http://genesys.com/customer-care.
- Genesys Documentation website at http://docs.genesys.com/.
- Genesys Documentation Library DVD, which you can order by e-mail from Genesys Order Management at orderman@genesys.com.
Document Conventions
This document uses certain stylistic and typographical conventions—introduced here—that serve as shorthands for particular kinds of information.
Document Version Number
A version number appears at the bottom of the inside front cover of this document. Version numbers change as new information is added to this document. Here is a sample version number:
85fr_ref-exta_04-2014_v8.5.001.00
You will need this number when you are talking with Genesys Customer Care about this product.
Screen Captures Used in This Document
Screen captures from the product graphical user interface (GUI), as used in this document, may sometimes contain minor spelling, capitalization, or grammatical errors. The text accompanying and explaining the screen captures corrects such errors except when such a correction would prevent you from installing, configuring, or successfully using the product. For example, if the name of an option contains a usage error, the name would be presented exactly as it appears in the product GUI; the error would not be corrected in any accompanying text.
Type Styles
Type Styles describes and illustrates the type conventions that are used in this document.
|
Type Style |
Used For |
Examples |
|---|---|---|
|
Italic |
Document titles Emphasis Definitions of (or first references to) unfamiliar terms Mathematical variables Also used to indicate placeholder text within code samples or commands, in the special case where angle brackets are a required part of the syntax (see the note about angle brackets on See Note: In some cases, angle brackets are required characters in code syntax (for example, in XML schemas). In these cases, italic text is used for placeholder values.). |
Please consult the Genesys 8 Migration Guide for more information. Do not use this value for this option. A customary and usual practice is one that is widely accepted and used within a particular industry or profession. The formula, x +1 = 7 where x stands for... |
|
Monospace font (Looks like teletype or typewriter text ) |
All programming identifiers and GUI elements. This convention includes: The names of directories, files, folders, configuration objects, paths, scripts, dialog boxes, options, fields, text and list boxes, operational modes, all buttons (including radio buttons), check boxes, commands, tabs, CTI events, and error messages. The values of options. Logical arguments and command syntax. Code samples. Also used for any text that users must manually enter during a configuration or installation procedure, or on a command line. |
Select the Show variables on screen check box. In the Operand text box, enter your formula. Click OK to exit the Properties dialog box. T-Server distributes the error messages in EventError events. If you select true for the inbound-bsns-calls option, all established inbound calls on a local agent are considered business calls. Enter exit on the command line. |
|
Square brackets ([ ]) |
A particular parameter or value that is optional within a logical argument, a command, or some programming syntax. That is, the presence of the parameter or value is not required to resolve the argument, command, or block of code. The user decides whether to include this optional information. |
smcp_server -host [/flags]
|
|
Angle brackets (< >) |
A placeholder for a value that the user must specify. This might be a DN or a port number specific to your enterprise. Note: In some cases, angle brackets are required characters in code syntax (for example, in XML schemas). In these cases, italic text is used for placeholder values. |
smcp_server -host <confighost>
|