Resolving 'UnmarshallException' Errors During Login - Identity Manager

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

This article addresses repeated net.sf.easyjson.UnmarshallException errors observed in the application logs during user authentication.

Repeated log entries similar to the following may appear upon login:

ERROR [stderr] (http-/0.0.0.0:8080-1) net.sf.easyjson.UnmarshallException: couldn't parse JSONERROR [stderr] (http-/0.0.0.0:8080-1) at net.sf.easyjson.JSONSerializer.fromJSON(Unknown Source)...ERROR [stderr] (http-/0.0.0.0:8080-1) at com.netegrity.llsdk6.imsimpl.passwordservices.PasswordBlobImpl.createBlobFromText(PasswordBlobImpl.java:64)

Environment

Identity Manager 14.5

Cause

This error occurs when the directory store contains legacy SiteMinder integration data. The %PASSWORD_DATA% metadata attribute—used for tracking password policies—may contain values that are unrecognized by Identity Manager, causing JSON parsing failures.

Resolution

To resolve this issue, the %PASSWORD_DATA% attribute must be cleared for the affected users.

Prerequisites

• Backup: Create a full backup of the directory store before applying any changes.
• Tooling: Use an LDAP browser (such as JXplorer) to interface with the directory store.

Procedure

1. Identify Affected Users: Use your directory monitoring tools or logs to identify the user accounts triggering the UnmarshallException error.
2. Clear Attribute:
   • Connect to the directory store using your LDAP browser.
   • Locate the affected user entry.
   • Identify the %PASSWORD_DATA% attribute.
   • Clear the value of this attribute for the user entry.
3. Validate: Attempt to log in to the Identity Manager User Console with the affected user account to confirm that the UnmarshallException error no longer appears in the logs.

Note: The %PASSWORD_DATA% attribute is metadata used for policy tracking; it does not contain the actual user password.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.