IAM Portal Connector Fails to Start - java.lang.NullPointerException - Identity Portal

Products

• CA Identity Manager
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

When starting the Identity Manager (IDM) connector within Identity Portal, the connector may fail to initialize. This failure results in a "Reload connector failed" error followed by a java.lang.NullPointerException in the Identity Portal logs.

 

The IDM connector in Identity Portal fails to start for the below reason:

Caused by: java.lang.IllegalArgumentException: Reload connector failed
        at com.idmlogic.sigma.connector.ca.CaimAdapterBase.reload(CaimAdapterBase.java:101) [sigma.connector.ca.im-0.0.2-SNAPSHOT.jar:]
...
Caused by: java.lang.NullPointerException
        at com.idmlogic.sigma.connector.ca.tews.WsdlInterceptor.removePortOperation(WsdlInterceptor.java:492) [sigma.connector.ca.im-0.0.2-SNAPSHOT.jar:]

 

Corresponding logs in Identity Manager indicate an issue with the following:

2020-06-30 12:39:00,946 ERROR [ims.default] (default task-15) Unable to get screen for com.netegrity.ims.tabhandlers.AssigneesTabHandler
2020-06-30 12:39:00,946 ERROR [ims.tmt.SchemaModKeyAdapter] (default task-15) could not get ObjectAdapterMetaData using property metadata on com.netegrity.ims.tabhandlers.AssigneesTabHandler@c543655
2020-06-30 12:39:00,946 ERROR [ims.tews6.SchemaGenerator] (default task-15) null: java.lang.NullPointerException

Environment

Identity Portal 14.x

Cause

This issue occurs when an Identity Manager task has Web Services enabled but is missing mandatory search screen information within its configuration tabs. During the connector's attempt to cache or intercept the WSDL for the task, the missing metadata causes the WsdlInterceptor to fail.

Resolution

To resolve this issue, identify and update the task with the missing screen configuration:

1. Enable DEBUG mode in Identity Manager to identify which task is causing the schema generation failure.
2. Review the Identity Manager logs for the ERROR [ims.default] Unable to get screen message to locate the affected tab handler (e.g., AssigneesTabHandler).
3. Export the Roles and Tasks XML and locate the identified task.
4. Ensure all tabs within the task have their required search screens defined.
5. Import the corrected XML, restart the Identity Manager environment, and then reload the Identity Portal connector.

Additional Information

Please note this can occur for any of the tabs.  In order to determine more information it recommended to put IDM in DEBUG mode and reproduce your issue.  This will help you in determining the task with the issue.

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.