Values in UDFs Auto-populated Using EL Expression Does Not Get Synced Up to LDAP in LDAP Sync Environment
Last updated on OCTOBER 16, 2016
Applies to:Identity Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In Self-registration and Create-User interfaces, one want to keep a UDF as hidden field, and populate it with concatenated values of what user has typed in on 2 other visible fields.
In other words, UDF = + dot +
For example, if
Tenant Code = HILL (user entered during registration)
UserID = HOLLAND1 (user entered during registration)
Then, OID attribute tenantUser should have Tenant User = HILL.HOLLAND1
The Tenant User and Tenant Code configured as UDFs in OIM and OID, and it works successfully when values are manually entered via "input Textboxes" in Self-registration and Create-User forms.
When a value is manually entered for Textboxes Tenant Code and UserID during registration, then Tenant User gets successfully populated in OID. This is shown in attached screenshot "Manual_entry_of_UDFs.png".
However, if manual textbox is substituted with EL expression to populate Tenant User based on input values entered on Tenant Code and UserID, then Tenant User attribute is NOT populated in OID. This is shown in attached screenshot "Expression_populated_UDFs.png".
In short, it looks like the stream of "request/response" carried from OIM to OID gets populated with value of a UDF, only if the UDF is "manually entered", and not when it is populated via EL expression.
Expected that Tenent User field be populated and pushed to OID server by LDAPSync
The issue can be reproduced at will with the following steps:
1. Use EL in UI customization to populate third field like = + dot +
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms