Unique Counter Variable in ISC

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi All,

Is there any variable mechanism to get unique counter for specific task in IdentityNow.
I want to submit a number from 100 to 999 while any provisioning request in plan to end system. The target system is not AD or Azure where we have uniquecounter.
The variable should be stored in ISC just like database sequence.

2

There is currently no mechanism in ISC to store a unique counter variable. But an idea has been submitted on the ideas portal and is under future consideration.

2 Likes
3

There is no such mechanism available currently. You probably can keep it stored on an dummy identity attribute and keep increasing everytime. but its a messy approach not recommended.

4

Hi @raghavchouda_wipro

Welcome to SailPoint Developer Community.

As confirmed by fellow experts, it is not feasible in ISC. Perhaps, if you can detail about your requirement to understand why you need this counter, we can suggest you the best possible approaches.

– Krish

5

Hi Everyone,
Thanks for reply. I understand that there is no mechanism for this at the moment.

I have business ask, there are 3 different sources for a single end system, because approval and certification model for different teams are based on group categories with the sources, lets say A, B and C sources. But on the same system we need to submit a variable with a number. Now, this number is not a self generated number via end system and if I want to create new user on the system, whether via A , B or C source. it need the account profile to include the number. Hence account requests submitted via ISC need this number to be unique and in sequence. End system has consumed some numbers already generated. We reserve some 10k numbers in sequence for SailPoint submitted request and then some will be generated via others integrations.

New attribute on the Identity profile could be solution, but it need to be searchable. and we exhausted the limit for Identity profiles already.

Thanks,
Raghav

6

Are you planning to add the unique counter to an account attribute to make the value unique?

7

Hi @raghavchouda_wipro

Coming at it from a different angle - If I read this right, it is the “next counter” that needs to be unique. So instead of doing the uniqueness check prior to provisioining, you may be able to script and store the “next unique counter” somewhere post-provisioning and use that in the account profile. Ideally, IMHO, I would actually store it on the target system in a single custom object, but if an object isn’t available and with a need to store it on ISC, there are probably a number of places it could go and then do a search to find the highest value.

8

Hi @iamnithesh , Yes I should be able to add it to Account Attributes & it should be unique across different sources.

Hi @j_place, you are correct, ideally it would be next unique value. However I can’t store in the target system as it do not support the variables. Creating a new custom object outside of ISC will lead us to maintain new place, which I would prefer at one place within ISC system. I am also thinking it from lead time to generate the new number. Also, if 2 or more simultaneous requests are made to update counter, how it will behave for uniqueness check in ISC.

Thanks,
Raghav

9

Have you tried the Account Profile Attribute Generator?

Inside the rule you can check for uniqueness using attrSearchCountAccounts method of IdnRuleUtil class. Attribute Name can be of a searchable attribute that is mapped to multiple sources

1 Like
10

Thanks Nithesh, We have tried this solution. It work is working, but this is another cloud Rule and it requires SailPoint support to implement.
Finally, we have come with new JDBC source which will store this new value of sequence and pass it to other source as account attribute with this unique number.

Regards,
Raghav

1 Like