This connector enables automated generation of custom attributes for identities in SailPoint Identity Security Cloud (ISC) using Apache Velocity expressions and advanced processing options.
The Attribute Generator connector allows you to:
Generate custom attributes for identities based on Velocity expressions
Apply various text transformations (case changes, normalization, space removal)
Create unique attributes with automatic conflict resolution using counter digit padding
Generate counter-based attributes with configurable digit padding
Process identities based on search queries
Support incremental aggregation with stateful operations
Reference previously generated attributes in subsequent attribute definitions
Requirements
Node.js (v14 or higher)
npm (v6 or higher)
SailPoint Identity Security Cloud tenant
Personal Access Token (PAT) with appropriate permissions
It’s more around unique identifiers and correlative IDs. It’s not safe to internally create these in provisioning time and this connector uses account aggregations to generate them in a controlled environment.
Every other attribute you can generate is for your own convenience. Most of it can be accomplished with transforms. Nevertheless, I could easily extend Velocity with new tools or add more complicated data processing transforms struggle with. This is an initial release so I’m open to suggestions.
Hey Fernando, Does the connector look through the uncorrelated accounts to insure unicity ? Im thinking about samaccounname or upn for example, the samaccountname can exist in the uncorrelated account on the Active Directory, is their a way to make the connector look through the uncorrelated acocunts before calculating the attribute?
Thanks for reaching out. The connector does not take into account uncorrelated accounts, no. It’s designed for identities only. However, don’t despair. The upcoming version of Identity Fusion does what you need.
Stay tuned. I plan to release it in the next few weeks.
@fernando_delosrios, i set up this connector to generate a counter based identifier using a Role to assign the Generate entitlement. It created the account on assignment of the Role however the identifier wasn’t populated until an aggregation was done. Is this as designed?