Siebel Analytics Installation and Configuration Guide > Siebel Analytics User Authentication and Security Setup > Configuring LDAP and ADSI Authentication in Siebel Analytics >

Configuring GSKit

GSKit supports Secure Sockets Layer. GSK uses a Java-based tool, IBM's IKeyMan Version 6.0, to create key database files for LDAP authentication over SSL. A key database file stores digital certificates based on the X.509 standard.

IKeyMan 6.0 can generate several kinds of key database files, but an LDAP client can use only key database files of the CMS type. The extension of this file type is .kdb.

To configure IKeyMan to enable creation of CMS key database files

  1. Install an IBM or an IBM-equivalent JDK.

    NOTE:  The correct version of Java is required for IKeyMan to work properly. See Siebel System Requirements and Supported Platforms for the correct version to use.

  2. Set JAVA_HOME to point to the directory where JDK was installed. For example:
    • On Windows, set JAVA_HOME=C:\Progam Files\IBM\Java13.
    • On UNIX, export JAVA_HOME=/usr/opt/IBMJava13.
  3. Remove the gskikm.jar and ibmjcaprovider.jar files from your ${JAVA_HOME}/jre/lib/ext directory.
  4. Make sure that ${JAVA_HOME}/jre/lib/ext directory has the following jar files:
    • ibmjceprovider.jar
    • ibmpkcs.jar
    • ibmjcefw.jar
    • local_policy.jar
    • US_export_policy.jar
    • ibmjlog.jar

      Look for these jar files and for ibmjsse.jar under GSKit installation path\classes\jre\lib\ext. Copy GSKit jar files to the ${JAVA_HOME}/jre/lib/ext directory.

  5. Register IBM JCE and IBM CMS service providers.

    Update the ${JAVA_HOME}/jre/lib/security/ file to add the IBMJCE provider and IBMCMS provider after the Sun provider. For example:


      A sample file for GSKit user can be found in GSKit Installation path \classes\

 Siebel Analytics Installation and Configuration Guide, Version 7.7, Rev. A 
 Published: 11 March 2004