SSO Plugin error java.lang.NullPointerException : null in iManager when managing SecureLogin

  • 3160837
  • 07-Mar-2007
  • 26-Apr-2012

Environment

Novell SecureLogin
NSL v 6
iManager

Situation

SSO Plugin error java.lang.NullPointerException : null
Error in iManager after choosing "Manage SecureLogin SSO" and browsing to and selecting a user
Problem only occurs for one user
Accessing and managing SecureLogin information for other users works without error in iManager
It is not possible to manage SecureLogin for the problem user with iManager
It is possible to manage SecureLogin infomation for problem user with SLManager

Resolution

Delete and recreate SecureLogin entries in eDirectory for the affected user following the steps below.

Steps:
1. Backup the current settings for the user by right clicking on the SecureLogin icon in the workstation system tray, and selecting Advanced, Backup user Information. An XML file will be created in the location specified.

2. Delete SecureLogin entries for the problem user by opening the"Other" tab under properties of the user in ConsoleOne, and deleting the attributes Prot:SSO Auth, Prot:SSO Entry, and Prot:SSO Entry Checksum.

3. Restore the user's SecurLogin settings by right clicking on the SecureLogin icon in the workstation system tray, and selecting Advanced, Restore user Information, and browsing to the XML file created in step 1. It is possible that a prompt will be received saying "An application with the same Id exists for one or more applications. Do you want to overwrite the application: with ?" Select "Yes" each time this prompt is presented . It is also possible that a prompt will be presented asking if you want to overwrite an application inherited from a container and create a new application on the user object. If this prompt is presented, select "No."


Note: Problem is suspected to be caused by minor data corruption in one or more of the SecureLogin entries stored in eDirectory. This occurred for the NSL admin who had been testing different versions of SecureLogin and going back and forth between NSL3.51.x and NSL6.0.x. By deleting and rewriting the data to eDirectory the corruption issue was resolved.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.