Hello, we trying to get some assistance on an attribute generator rule. It seems to pass both the validation and RDK. Our RDK test takes Joan as firstname, Arnold as lastname. This evaluates properly to joarnold as jarnold is taken. Anything clearly wrong with this rule? We always get object exists …

You can use the code function instead of getAccountAttribute since sAMAccountName is set up as the account name for the AD source. idn.accountExistsByDisplayName(application.getName(), username)

sAMAccount Attribute Generator rule

Identity Security Cloud (ISC) ISC Discussion and Questions

dstrachan (Derek Strachan) September 1, 2025, 1:47pm 6

This worked great. Thank you. Our issue was not having the duplicate identity synced to ISC and just having it present in AD

1 Like

Topic		Replies	Views
Unable to generate samAccountName via AttributeGenerator Rule ISC Discussion and Questions rules , identity-security-cloud , attributes	10	733	October 12, 2023
UserName Generator Issue ISC Discussion and Questions identity-security-cloud	3	547	April 13, 2024
Leveraging Another Create Profile Attribute in an Attribute Generator Rule ISC Discussion and Questions rules , identity-security-cloud , provisioning	4	530	January 1, 2024
Unable to generate incremental samAccountName in AttributeGenerator Rule ISC Discussion and Questions identity-security-cloud , provisioning , attributes	6	605	May 7, 2024
sAMAccountName Generator ISC Discussion and Questions	15	4538	July 19, 2023

sAMAccount Attribute Generator rule

Related topics