IG connector to IM: failed to get object type configuration
search cancel

IG connector to IM: failed to get object type configuration

book

Article ID: 232080

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Governance

Issue/Introduction

We have an issue creating an IDM Connector within an IG Universe.  

We have checked the settings several times and if we missing anything, we cannot figure out what.

Things that work.

- IG 14.4 can connect to an instance of IM 14.2 without issues.  But is seems the same settings do not work for IM 14.4.

- If we mistype a password, that puts a different error in the logs, so seem to think auth is OK

- If we specify a wrong FIPSKeyFile, then that puts a different error in the logs, so seem to think we have matching FIPS.dat.  

 

Things we have tried:

In IM:  Delete Web Services Configuration, IMRCM configuration  (tried this several times)

In IM & IG:  Changed authentication from OpenID Connect back to native authentication.  (no effect)

 

Log snippets:

IM:  

Failed to marshall managed object response
        at com.ca.iamframework.webservices.util.ManagedObjectUtil.marshallPayload(ManagedObjectUtil.java:740)
        at com.ca.identitymanager.webservices.api.ConfigurationResource.getConfiguration(ConfigurationResource.java:148)
        at sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0 
Caused by: [facility=4 severity=3 reason=0 status=6 message=Unrecognized command]

 

IG:

 2021-08-18 15:48:13,276 ERROR [stderr] (default task-12) ERROR WebServiceHandler WebServiceHandler.getJSONObject: 3 attempts have failed to get object type configuration from IM. Return status is: Internal Server Error

 

Environment

Release : 14.4

Component : IdentityMinder(Identity Manager)

Resolution

Resolved by new hotfix:

HF_DE515737.zip