Change from ODBC to LDAP session store in sm.registry
search cancel

Change from ODBC to LDAP session store in sm.registry

book

Article ID: 274133

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

Changing the session store from ODBC to LDAP without using smconsole.

SMLDAPSETUP can be used for policy stores, but doesn't work for session stores.

Environment

Release : 12.8

Resolution

Configure the LDAP server settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\LdapSessionServer]
"Server"="10.0.0.1:44443"
"AdminDN"="cn=user,ou=example,c=us"
"AdminPW"="{RC2}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
"SSRootDN"="ou=example,c=us"
"Use SSL"=dword:00000000
"MaxConnections"=dword:0000000a
"Enabled"=dword:00000001
"Version"="5.0"
"Use Default"=dword:00000000

AdminPW must be encrypted prior to entering it into the registry, using one of the following methods:

  1. Create a temporary user directory and configure it with the password for the session store and copy the encrypted password over to the session store registry location.
  2. On another system that has smconsole working, configure the settings and copy the encrypted password field to the server you are working on.
  3. If the password for the existing session store (or another type of store) and the new session store happen to be the same, copy the encrypted password from the existing key location to the new location.)

Configure the ODBC settings (all other ODBC settings can remain the same):

[HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\Database\SessionServer]
"Enabled"=dword:00000000
"ProviderNamespace"="LDAP:"