JDBC Application Onboarding

Which IIQ version are you inquiring about?

8.5

Share all details about your problem, including any error messages you may have received.

Hello All,

I am working on JDBC application onboarding in SailPoint. We have requirement to generate the account name in the given format for any new user account to be created from SailPoint.

  • Account Name - + <4 random digit> (Account name must be unique across the application account)

I have created provisioning policy and attached the field value rule with the above logic to generate value. However, when I try the provisioning, we see that account link shows <???> instead of the account name and provisioning fails.

Troubleshooting Steps

1. Verify the Rule Returns a String

Check your rule’s logic and especially the return statement—ensure it’s always returning a non-null string.

2. Test in an Isolated Environment

Hardcode a value (return "+1234") as a sanity check. If this works, the problem is with your randomization/uniqueness logic.

3. Log Output

Add SailPoint logging to your rule wherever you feel it is causing the issue.

log.info("Generated account name is: " + accountName);

return accountName;

4. Attribute Mapping

Ensure your provisioning policy is using the rule correctly for the account name attribute. Double-check the attribute name and mapping.

5. Check for Exceptions

Look in the SailPoint logs for stack traces or error messages—an error in rule execution can produce the <???> output.

@toshal_selokar- You can give it a try on these aspects and provide more details if you feel the issue still exists.

1 Like

Hi @toshal_selokar

If the rule logic is working correctly then the possible issue would be with the fieldName in the account schema mismatch with what you have added in the provisioning policy.

E.g., Nativeidentity attribute name in schema - UID then you should add exact same in the provisioning policy.

Hi @pallavi , thank you! It worked.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.