Mapping an Identity Attribute Rule
Key Takeaways
Use a direct mapping or transform when it expresses the data requirement. An Identity Attribute Rule returns one calculated identity attribute.
An Identity Attribute Rule runs in the cloud, with read-only platform access and no direct access to on-premises connectors.
After installation, select Complex Data Source and the named rule in the identity attribute mapping.
Preview boundary cases and verify processed values. The rule review process and a successful provisioning check answer different questions.
Choose the mapping at the point of need
An identity attribute mapping specifies what value an identity attribute should have. An engineer can copy a value from a source account, apply a supported transform, or use an approved Identity Attribute Rule where more complex logic requires it. Choose the simplest feature that represents the desired calculation and document the source values it relies on. An account password or a directory write belongs to a downstream provisioning operation. Calculating an identity attribute does not itself send a command to a target.
| Use case | First mechanism to evaluate |
|---|---|
| The source provides the exact family name | Direct mapping |
| Convert a source string to lower case | Supported transform |
| Derive an identity value from complex policies using available identity context | Approved cloud Identity Attribute Rule if supported transforms cannot express it |
| Establish a manager relationship | Manager correlation configuration or its documented rule |
| Change a provisioning plan before it is sent | Before Provisioning Rule |
Trace what an Identity Attribute Rule can do
SailPoint documents this rule as a cloud-executed operation. It has read-only access to platform data through the available context and helpers, and no direct access to an on-premises source or connector. The rule receives an identity, the attribute’s oldValue, and documented utilities. It returns the calculated attribute value. Use a value appropriate for the mapped attribute type. Validate inputs before comparing them or returning a value, including an absent source field, empty string and mixed formats if those are possible. The old value is the previous value of this identity attribute. Use it as a fallback only if the policy specifies when preservation is valid.
Suppose a profile needs a lifecycle calculation that uses already calculated identity attributes. SailPoint documents that the lifecycle state attribute is computed last during refresh, so a rule for it can refer to other identity attributes. When the policy returns a lifecycle state, return the configured technical name with its exact case. Before implementing, agree on which branch handles missing or inconsistent dates. For another mapped attribute, check the documented inputs and do not assume all other mappings will have the same order.
Attach the rule and test concrete outputs
Once the rule is installed, find the relevant attribute in the identity profile mapping, choose Complex Data Source in the source selector, and select the rule under Transform. Save, preview representative identities, and apply changes after validating the expected values. Verify the effective value on the affected identity after processing. For any automated access that depends on the value, inspect the separate operation and target result. Cloud rule logging is currently visible only to SailPoint personnel, so collect the reproducible identity inputs and expected vs actual output when escalating.
Imagine a rule that derives a string-valued attribute called supportTier from eligibility conditions maintained by the company. The policy says that a worker in region East and marked onCall=true should return Tier2. A worker in East with an explicitly false designation should return Standard. If an East worker’s designation is absent, this business policy returns Pending while the data owner resolves the gap. Test an on-call worker from a different region as well. Expect Standard under the stated rule, even if that identity’s previous value was Tier2. These sample values are the company’s policy outputs. Any role using this field must be evaluated separately. Where the input fields come from another source, make sure those values are present in the identity model. A rule that attempts to open a new connection to the local scheduler exceeds the documented cloud context. Bring the eligible input into the model through a supported path first.
The cloud rule review is about platform integrity and the intended rule use case. It does not demonstrate that a particular organization’s branches return the values its policy expects. Keep concrete examples and the expected output beside the configuration, especially at transitions or when multiple inputs disagree. This also helps distinguish a calculation defect from a correct result followed by unsuccessful target provisioning.
See SailPoint’s Identity Attribute Rule, cloud rule review responsibilities, identity profile mapping, and lifecycle technical names.
An organization has installed a cloud Identity Attribute Rule. Where is it selected to calculate an identity attribute?
In the VA’s proxy configuration
In the target application’s Account ID setting
In the profile attribute mapping using Complex Data Source and the rule name in the Transform selector
In the Service Desk status mapping
A proposed identity attribute rule tries to read a file directly from an on-premises connector at runtime. Which design fits this execution context?
Aggregate the approved input through a supported connector and base the rule on available cloud identity data
Have the rule automatically elevate to the appliance root account
Give the existing cloud rule a directory password so it can call the connector directly
Replace the identity attribute with the source’s account deletion threshold
Sections you finish are checked off in the contents.