SiteMinder : Usage and purpose of smjndisetup.sh

Products

• SITEMINDER

Issue/Introduction

smjndisetup utility is used to update the password external bind user id's password in the AdminUI's local database.

[smuser@servername] ./smjndisetup.sh
usage: smjndisetup.sh [-?] [-rp] [-s | -c]  [-u <user name>] [-p <password>]
 -?,--help                  print this help message
 -rp,--reset-password       specify to reset a previously established directory password
 -s,--silent                run in silent (non-interactive) mode
 -c,--no-confirm            implicitly accept all confirmations (implied by -s)
 -u,--user <user name>      the new directory user name
 -p,--password <password>   the new directory password
[smuser@servername] ./smjndisetup.sh --reset-password
ERROR StatusLogger Reconfiguration failed: No configuration found for '33833882' at 'null' in 'null'
Enter the user name (hit Enter to accept the default 'Bind User ID'):
><LDAP Bind User ID>
Enter the password:
>
java.lang.IllegalArgumentException: Illegal character in scheme name at index 0: 10.0.0.1:389
        at java.net.URI.create(URI.java:852)
        at com.sun.jndi.ldap.LdapURL.validateURI(LdapURL.java:216)
        at com.sun.jndi.ldap.LdapURL.fromList(LdapURL.java:193)
        at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:76)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:695)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
        at javax.naming.InitialContext.init(InitialContext.java:244)
        at javax.naming.InitialContext.<init>(InitialContext.java:216)
        at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:101)
        at com.ca.commons.jndi.JNDIOps.openContext(JNDIOps.java:777)
        at com.ca.siteminder.webadmin.configuration.LDAPUtilities.testConnection(LDAPUtilities.java:65)
        at com.ca.siteminder.tools.jndisetup.JNDISetup.resetPassword(JNDISetup.java:527)

Environment

R12.8.x

Policy Server AdminUI

Cause

In this case the User store's bind user's password is updated using external tools like PAM , which would take some delays in password sync and causing the exception as mentioned in the description.

Resolution

Updating the below  attributes as per the of the User store used for external user directory from the AdminUI.

Universal ID (R)
Disabled Flag (RW)    
Password (RW)    
Password Data (RW)