Save As Users Are Unable To Approve Using LDAP Password (AUTH_SRC as AGILE_DB)
Last updated on AUGUST 08, 2017
Applies to:Oracle Agile Product Collaboration - Version 184.108.40.206 and later
Information in this document applies to any platform.
***Checked for relevance on 22-May-2014***
Use-Case: Some users are created using the SaveAs feature in Agile, then followed by an LDAP sync
Certain users are unable to "approve" in Agile, indicating that the users approval password is invalid - despite fact that flag is set to allow login password as same for approvals and we have verified that these users are using exact same credentials for login and approval.
The AGILEUSERS table shows AUTH_SRC as AGILE_DB for users having issues approving and for others who are able to approve - their AUTH_SRC setting is xxxx_LDAP. This seems significant, but we are unable to determine how this user attribute is configured/managed.
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