Building a Source Create Account Policy
Key Takeaways
Create Account defines how new target account fields are populated for a source.
Use connector requirements to choose fields, constraints and target formats. Test the actual creation in a sandbox.
Place a field that supplies another field’s value earlier in the definition.
Verify provisioning and aggregation separately when a target field appears in one definition only.
Start with the source’s account contract
When an identity receives access and has no account on that source, SailPoint uses the source’s Create Account definition to build the new account’s attributes. The trigger can be an access request, a role or a lifecycle state. In automatic direct-connect provisioning, the supported connector sends the write. When SailPoint cannot push changes to a flat-file source, it creates a work item with the attribute values for a person to use for manual fulfillment.
Open the source under Admin > Connections > Sources and select Create Account in Account Management. Read the connector’s account creation defaults and the target’s requirements. For each intended field, confirm its name, type, rule for blanks, whether it must be unique, and a representative source value. Verify that the connector supports writing that field for account creation. The appropriate uniqueness checks and the chosen attributes depend on the target.
| Mapping option | Choose it when |
|---|---|
| Identity Attribute | Copy a calculated or promoted identity value directly, such as Work Email into a target mail field |
| Generator | Create a value using a documented generator and its configured inputs, such as a unique directory account identifier |
| Static | Supply a constant or a supported Velocity expression referring to an account attribute defined earlier |
| Disable | Deliberately omit the field on create after confirming it is optional |
| Policy API with transform | Implement a supported calculation that needs more than the source page exposes |
The Static option in Create Account can reference earlier account values by name. It cannot directly reference identity attributes there. To use an identity value directly, select the Identity Attribute mapping, or use the supported identity attribute transform input where a policy calculation requires it. Account creation evaluates fields in their listed order. If login is computed first, an expression using $login for a later target field can use that account value. Move the dependency higher in the list and re-run the create test before using the result elsewhere.
Work an Active Directory create
Consider a sandbox Active Directory user creation. The connector’s defaults use ObjectType set to User for a user, a unique distinguished name (DN) generator, a separate sAMAccountName generator, and a Create Password generator matched to the source’s assigned password policy. Review the container in the DN pattern. SailPoint’s connector instructions require changing the default organizational unit (OU) placeholder. Use a container the sandbox service account can write to and test a directory name collision. Verify the resulting DN and sign-in name independently because the target has distinct fields for them.
Suppose the organization requires that a new target account have mail set from Work Email and that a required directory flag have a fixed value. Configure the first as an identity mapping and the second as a static value allowed by the connector. If the organization requires the manager, check which manager field and value the connector supports. For Active Directory creation, the documented default is Get Manager LDAP DN, where LDAP stands for Lightweight Directory Access Protocol. A human-readable manager string would be unsuitable for that target field.
Validate written and retrieved attributes
SailPoint allows you to include a source-supported attribute in Create Account even when it is absent from the account schema. Add the field under its exact source name. To retrieve that attribute through aggregation, add it separately to the appropriate schema if supported. Conversely, the presence of a field in the account schema tells you how SailPoint reads it. Configure creation input separately for values the target must receive.
Run the test with a representative identity that has no existing account on the source. Confirm nonblank required inputs and the expected generated name. Verify the actual target entry, its attributes and grant, then use a supported aggregation to validate the returning account data if the field is intended to be readable. Account create fields need no Before Provisioning Rule merely to supply a new attribute. The official rule guidance assigns new account fields to the account creation profile and reserves the cloud rule for changes to an outgoing plan.
See SailPoint’s source Create Account options, Active Directory default mappings, and Before Provisioning Rule.
A Create Account policy builds a target address using an already calculated login account field. How should the named dependent fields be ordered?
Place the login calculation above the field that uses it
Place the target address above the login so the later value can resolve it
Place the fields in any order and change the identity profile priority
Store the login only in the entitlement schema
A target supports writing a department code for account creation, but that code is absent from the account schema. A pilot must set it on create and retrieve it during aggregation. What configuration fits?
Configure only an access profile with that name
Add a source create mapping for the exact supported field and separately configure the account schema to retrieve it
Set the value only in the account schema and assume the creation policy will infer it
Change the Before Provisioning Rule to introduce the field and skip account/schema configuration
Sections you finish are checked off in the contents.