Oracle BPM Parametric doesn't honor Group or Role based Grant Conditions correctly
(Doc ID 1962914.1)
Last updated on MAY 16, 2023
Applies to:
Oracle Business Process Management Suite - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
Parametric roles do not correctly evaluate Role or Group based grants as a condition.
Example replication steps:
1. In the workspace create a parametric role. Create it exactly to look like the screenshot shown below.
2. Create two users in the weblogic embedded ldap. paraUser1 and paraUser2
3. Modify paraUser1 and paraUser2 to have a displayName property of: paraValue1
4. Deploy the attached project.
5. Assign paraUser1 to the role: TestParametricProject.ParaRole
6. Test the project through em. The service takes two arguments. Set them as follows:
displayName: paraValue1
appRole: TestParametricProject.ParaRole
7. Launch the audit trail and click on the human task. It will show the task was assigned to both users despite paraUser2 not being assigned to the role TestParametricProject.ParaRole, which is a condition of the parametricRole
2. Create two users in the weblogic embedded ldap. paraUser1 and paraUser2
3. Modify paraUser1 and paraUser2 to have a displayName property of: paraValue1
4. Deploy the attached project.
5. Assign paraUser1 to the role: TestParametricProject.ParaRole
6. Test the project through em. The service takes two arguments. Set them as follows:
displayName: paraValue1
appRole: TestParametricProject.ParaRole
7. Launch the audit trail and click on the human task. It will show the task was assigned to both users despite paraUser2 not being assigned to the role TestParametricProject.ParaRole, which is a condition of the parametricRole
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |