Choosing Policies for Provisioning Operations
Key Takeaways
Choose the policy for the operation and confirm that the connector supports it on the current source type.
Create Account supplies new account attributes. Additional operation policies, such as UPDATE, can be managed through the provisioning policy API.
A policy can supply fields to an outgoing operation. The connector still needs its operation configuration and target privileges.
Use the cloud Before Provisioning Rule for a justified change to an outgoing plan, and use the source’s policy to compute new account fields.
Separate required fields from execution
A provisioning policy defines fields and calculations for a source operation. For Create Account, the policy can generate an identifier and set the required values. For a supported Update operation, a separate policy can supply fields for the update. Read the supported usage types in the SailPoint application programming interface (API) documentation and use the applicable connector’s instructions for the operation. A usage type in a schema expresses a possible policy purpose. Acceptance of a policy definition alone establishes neither connector implementation nor permission to write on a target.
When writing a plan, distinguish three concerns. First, pick the intended account operation based on the person’s change and existing target account. Second, determine what values that operation needs and how it should obtain them. Third, identify the connector function that takes the request and changes the target. A policy containing a valid field is only one part of that path. Some connectors expose their own operation configuration and differ by variant or deployment.
| Requirement | Place to start | Outcome to verify |
|---|---|---|
| Create a missing account with a generated identifier | Source Create Account definition and connector creation capability | Correct new account and required values |
| Supply a calculated account field for a supported update | Operation-specific provisioning policy and connector update mapping | Correct field on the existing intended account |
| Keep an eligible field continuously aligned to the mapped identity value | Direct Create Account mapping and Attribute Sync | Expected field on existing correlated accounts |
| Issue a distinct enable or disable action | Check connector operation support and the appropriate trigger or policy | Existing account’s actual enabled status |
| Adjust the outgoing plan for a condition that rules must express | Supported Before Provisioning cloud rule after review | Intended plan variation and corresponding target action |
Work the connector example
A team uses a virtual-appliance-based Java Database Connectivity (JDBC) source. Enable Configure Provisioning Operations in the Connector to use the documented query settings. These include a Structured Query Language (SQL) statement or stored procedure for Create Account and an Update Account configuration based on the provisioning plan. Assume a finance database needs a business key and a given name for a new row. Configure a Create Account definition to supply these values. In the connector’s Create Account query or stored procedure, use the plan values to write the row. Confirm the connector can return the correct native identifier or obtain it using the documented mechanism when it is not supplied in the plan. Verify that a test create inserts one row and that a later operation targets that exact native identity.
Now assume an existing account must have its email changed in a supported update. Changing only the Create Account mappings leaves the runtime update path to verify. Review the applicable Update Account policy and connector configuration. Capture the update plan and check that it addresses the intended row with the expected value. A read query returning the expected person can demonstrate identification, but the write also needs the correct operation and permissions. Separately verify the native result.
Choose the smallest supported customization
SailPoint describes the Before Provisioning Rule as a cloud rule that modifies a plan before the connector receives it. The rule has read-only access to platform data and lacks direct access to the on-premises connector. Use a policy field or an identity attribute transform when you need a new account attribute. Use an Identity Attribute input to supply source-derived values in a provisioning policy transform. If the plan needs a database value that the identity does not already have, bring that approved input into the model through aggregation and mapping before applying the policy. Verify that the identity value is available when the policy evaluates it.
For a rollout, inspect which policy is already present for the intended usage type. Use the documented create or update operation as appropriate and retain a copy of the known-good configuration. Respect the documentation for the selected API version, including any experimental endpoint requirements. Exercise the intended operation in a sandbox, then confirm the account activity and native state. A passing create test leaves update and other operations to be tested on their own data and permissions.
See SailPoint’s source policy setup, policy API operations, policy transforms, JDBC provisioning query settings, and Before Provisioning Rule.
A writable JDBC connector must change email on an existing database account. The list of field calculations must be updated for that supported operation. What should the engineer configure and test?
Only the Create Account policy, using an identity without an account
The applicable update policy and the connector’s update behavior using the intended existing account
Only the account aggregation query, then sample its result
Only an entitlement description with the new email string
A new target field must be set when an account is created. The source supports the field and its value is derived during provisioning. Which mechanism fits the documented boundary?
Add a supported field calculation to Create Account and verify a new account provisioning event
Have the core cloud Before Provisioning Rule open a direct connection to the target
Set only the account schema and derive the value during certification
Create a manager correlation rule to add the account attribute to the provisioning plan
Sections you finish are checked off in the contents.