This content has been marked as final. Show 6 replies
As per Oracle docs, this is an existing issue.
Take a look on the below Oracle release note:
Go through the Patch1 doc/release note and verify if it is fixed or not.
Thanks for your reply as I have mentioned, the same scenario is working fine in my test system so apparently it is not the issue that you have mentioned......
The only difference that I have noticed in the properties of the group form in between My test system and production is that
-in test the lookup field is having no value it is blank
-where as in the production system it is having a value
in the design console for the both there is no difference all is same for both
I have noticed the following,
If I assign the Entitlement or assign Group from Modify Account it is assigned properly with the proper name defined in the AD (Upper+ Lower Case i.e “IDMGroup”) and shown in under Entitlements Tab and in Groups Form.
During AD User Target Reconciliation the “Group Name” attribute value changes to all to UPPER case i.e IDMGROUP along with the complete DN. (See Screenshots) .
Since there is a trigger defined in the UD_ADUSRC table that checks and compares the Group Name value to be placed in the Entitlements table, I believe it fails to make the comparison with the existing value that is in mixed characters.
Following is the trigger
CREATE OR REPLACE TRIGGER UD_ADUSRC_ENT_TRG
OR UPDATE OF UD_ADUSRC_GROUPNAME
FOR EACH ROW
WHEN INSERTING THEN
WHEN UPDATING THEN
IF :NEW.UD_ADUSRC_GROUPNAME != :OLD.UD_ADUSRC_GROUPNAME
WHEN DELETING THEN
I believe that if we can identify that why during the reconciliation the Group Name is being reconciled in uppercase? It can solve the issue.
OK, I have got it fixed.
Could you explain how you solved this? I'm experiencing the same issue now.