What problem are you observing?
Following the migration of the Create Policy page to the Source Configuration page, an issue has emerged affecting attribute references throughout the policy. When any minor modification is made to the policy from the Source Configuration → Create Account page (e.g., altering an identity attribute for a field), previously declared attribute references in all fields are automatically removed. This issue is not limited to specific fields like distinguishedName but affects all fields where attribute references are utilized.
What is the correct behavior?
The expected behavior is that all declared attribute references in any transforms for any field should remain intact when unrelated modifications are made to the policy. For instance, the “ouDetails” reference should persist in the distinguishedName field even when modifying other attributes, such as changing the value for physicalDeliveryOfficeName from “Department” to “Title”.
What product feature is this related to?
This bug is related to the Create Account provisioning policy. The issue specifically arose after the recent migration of the “Create Account” page to the Source Configurations page. This migration has impacted the behavior of attribute references within the policy settings.
What are the steps to reproduce the issue?
Step 1: Deploy a create provisioning policy for Active Directory Source.
Step 2: In the distinguishedName field, use a static transform with the value “$cn,$ouDetails”.
Step 3: Declare “ouDetails” as a reference to identity attribute under the attributes section for the distinguishedName, above the value.
Step 4: Navigate to the new Source Config → Create Account page.
Step 5: Make a small modification to the policy, such as changing the identity attribute for a field (e.g., changing the value for physicalDeliveryOfficeName from “Department” to “Title”).
Step 6: Save the changes.
Step 7: Observe that the “ouDetails” reference previously declared under attributes for distinguishedName has been automatically removed.
Do you have any other information about your environment that may help?
This issue was initially identified on a sandbox tenant. Subsequent testing on a partner-demo tenant reproduced the same behavior. Further investigation on a devrel-demo tenant, which has not been updated to the new configurations page (where “Correlation” and “Create Account” still reside on the source page), did not exhibit this issue.