Oracle Identity Governance (OIG) Generic Rest Connector 12c __ACCOUNT__.SEARCHOP Does Not Use Attribute Names Successfully (Doc ID 3074363.1)

Last updated on FEBRUARY 27, 2025

Applies to:

Symptoms

 Generic rest connector does not replace the placeholder with the actual value of the attributes

From the Rest Connector documentation:
"nter the relative URLs for all operations of each object class.

Enter a value for this parameter in one of the following formats:

For attributes: OBJ_CLASS.OP=REL_URL

For special attributes: OBJ_CLASS.ATTR_NAME.OP=REL_URL

For attributes that have the same relative URL for multiple operations: OBJ_CLASS=REL_URL or OBJ_CLASS.ATTR_NAME=REL_URL

If you want to filter records based on a filter criteria during reconciliation, then use $(Filter Suffix)$. Here, replace $(Filter Suffix)$ with the filter criteria that you specify as part of the Filter Suffix attribute of the scheduled job.

If you have to pass the unique ID of the user as part of endpoint URL, use $(__UID__)$. Here, replace $(__UID__)$ with the unique ID of the user.

If you have to pass any attribute other than the unique ID of the user, then represent it in one of the following formats:
For a single-valued attribute: $(attr_name)$

Here, replace $(attr_name)$ with the name of the attribute in the target system.

For an embedded object: $(OBJ_CLASS.ATTR_NAME)$

For example, $(__GROUP__.id)$.

End point specified in relURI's should be without a host name. Host name should be specified in basic configuration and it will be appended through the code in run time."

Need: Send an attribute from the account in the URL

Configuration:

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.