I'm Anil Bandamudi, started working on sailpoint IdentityIQ in Jan 2010. I have experience on web applications development and also sun identity manager implementation before coming to this product implementation.
The Sun IDM experience is the plus in getting the knowledge on sailpoint product. I have installed identity IQ 3.0 p18 version in my machine to start knowing on this product. Actually we don't have much documentation in starting days about features and real time usage. We analysed it later. I'm listing some of the important items
Authoritative resource and non authoritative resource
Aggregation
Correlation
Certification
the above 4 items are nothing for the experienced guys on this product. of course, but as part of our Research and development we concerned on the following
- what is the flow
- where to start the process and what are the steps in identity life cycle
- what are the types of resources and their connectors
- how should we modify the actual data before creating/correlating identity.
- what are the advantages of this product over sun IDM(not only sun, we have CA,novel, tivoli and so many products -- I mentioned sun idm bcoz I have some experience on this product)
I'll write brief explanation about these in next post
Have a great day!!!!!
hey.. plz share further details and concepts of sailpoint
ReplyDeleteHey Brother,
ReplyDeleteThanks for the timely post,
at least for me . I have encore time wondered about the transition, but somehow did not dare, because the information I came across very controversial.
But today, after reading your article I’m very confident to take up any challenges.
Appreciate your effort for making such useful blogs and helping the community.
Obrigado,
Mahesh
Hi There,
ReplyDeleteThank you SO MUCH! I was actually holding my breath as I followed these directions. It worked beautifully!
It's great to utilize the power of internet with the available free blogs.
Appreciate your effort for making such useful blogs and helping the community.
Regards,
Irene
Hi Bru,
ReplyDeleteThank you for update. From now onward I start to use this blog in my training practice. Thank you for explaining each step in screen shots. I use blogs for my easy reference which were quite useful to get started with.
I modified code as per your suggestion,
Code is working fine when I passed 1 Access request id( identityRequestId ="0000012355";) record.
But it is failing when I try using Multiple Access request id's( String identityRequestId=renderCache.get("AcceReqID");)
Sailpoint idm training
May be some problem with my code only.Thanks a lot.
Even I tried this logic also,it is also working for single access request id only
But great job man, do keep posted with the new updates.
Thank you,
Ajeeth
Hi Bandlamudi ,
ReplyDeleteThanks for the post, it’s a great piece of article. Really saved my day.
Based on my research, this would be the order in which the rules are called. Some rules may be skipped, depending on the aggregation task or refresh task options selected:
Aggregation Rules
Sailpoint tutorial (applies to all application types which support the rule type)
1) Customization Rule
2) Correlation Rule (does not run when an account has been ""optimized"" or when an account has been manually correlated to an identity)
3) Creation Rule (only if correlation was unsuccessful and the task option ""Only create links if they can be correlated to an existing identity"" is not checked)
4) Manager Correlation (only if: the source account has changed (i.e not optimized), or the task attribute alwaysRefreshManager=true. Can be bypassed by setting task attribute noManagerCorrelation=true)
5) Managed Entitlement Customization Rule (only if ""Promote managed attributes"" is selected on the aggregation/refresh task and only runs the first time a ManagedAttribute is created)
Provisioning Rules (applies to all application types which support the rule type)
1) Before Provisioning Rule (if set, always runs just before the connector's provision method is executed)
2) After Provisioning Rule (if set, always runs just after the connector's provision method is executed)
Connector Rules (in your case, only applies to the SAP HR connector. Not all application connectors support this)
1) Provisioning Rules is called during the connector's provision method (after the ""Before Provision Rule"" but before the ""After Provisioning Rule"")
Once again thanks for your tutorial.
Many Thanks,
Preethi.
Hi There,
ReplyDeleteThanks for the tip, appreciate it. Your article definitely helped me to understand the core concepts.
I’m most excited about the details your article touch based! I assume it doesn’t come out of the box, it sounds like you are saying we’d need to write in the handlers ourselves.
Is there any other articles you would recommend to understand this better?
You can delete the sailpoint tutorialCertification Group object from iiq console using certification id, if the certifications has same name.
Command syntax (to be run on iiq console):-
>delete Certification Group
Similarly you can delete Certification object.. just specify the type of object as Certification.
Very useful article, if I run into challenges along the way, I will share them here.
Best Regards,
Abhiram