0
Fixed

EVB - IDB API Issue

Richard Green 1 year ago • updated by anonymous 12 months ago 6

Hi Guys,

I'm currently having an issue communicating with the IDB API from Event Broker. Not sure if this is IDB or EVB.

I'm getting the following error trying to run an API operation:

Operation Full Import - DAMS Contact Connector with id a1508248-0161-46a0-a703-a1cad6cfc8ed failed in the operation list IDB - DAMS Contact - Full Import with id bae408b8-0b38-495f-a92a-4b1a8319f15b for the following reason. This is retry number 0: Unify.Product.EventBroker.RestAPIAgentUnexpectedStatusException: Response code NotFound doesn't match expected response code NoContent.
 at Unify.Product.EventBroker.RestAPIPlugIn.Execute()
 at Unify.EventBroker.PlugIn.Audit.OperationAuditingDecorator.Execute()
 at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)

I have the following agent configured (Have tried IDB Port with no change):


And the following API config in IDB:


IDB v5.2.0 R2

EVB v4.0.0 R1

IDB and EVB are on the same box, and i can hit the swagger page for the rest API.

Nothing applicable in the IDB logs or Event Logs (even enabled diagnostic logging in IDB)

Answer

Answer

Richard, the patch provided by Curtis should be removed when you upgrade to v5.2.0 RTM - as the URL format was fixed to be in line with the format in v5.1.

Fixed

Hi Richard,

Please try placing the following patch DLL into the Event Broker Services directory and re-attempting the operation.

Unify.EventBroker.PlugIn.RestAPI.dll

Please note that this ONLY affects Identity Broker v5.2+. Please don't use this patch against an Identity Broker v5.1 instance.

The issue is that the request relative URI for triggering Import All operations against connectors has changed from

IdentityBroker/api/1.0/Connector/ImportAll/{connector ID}

to

IdentityBroker/api/1.0/Connector/ImportAll?id={connector ID}

An alternative workaround for now would be to manually create a Rest API operation with this new relative URI, Request Type POST, Expected Response Status No Content.

Yep, confirming that patch has fixed the issue :)

Excellent, thanks for confirming.

Answer

Richard, the patch provided by Curtis should be removed when you upgrade to v5.2.0 RTM - as the URL format was fixed to be in line with the format in v5.1.