tag:blogger.com,1999:blog-1354333581879889472.post2587269329157255453..comments2023-05-08T05:38:47.067-07:00Comments on Identity and access management reflections: Contractor life cycle managementAnonymoushttp://www.blogger.com/profile/11665304931618052376noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1354333581879889472.post-76361496101041401212012-01-09T12:14:15.216-08:002012-01-09T12:14:15.216-08:00Indeed a great article Martin. You would ,however,...Indeed a great article Martin. You would ,however, also want to consider including the case where a contractor is hired as a full-time employee and AD or other such resources (that are given to both a contractor and full-time emp) may fail to provision since the auto-generated logins which also form the DNs, stop OIM from creating a similar DN for the contractor who is now hired as a full-time employee.Abhishekhttps://www.blogger.com/profile/12674943999057361785noreply@blogger.comtag:blogger.com,1999:blog-1354333581879889472.post-51410275406484828222011-01-23T23:42:19.377-08:002011-01-23T23:42:19.377-08:00Great article! During analysis I would recommend t...Great article! During analysis I would recommend the company to create a repository for contractors rather than entering them directly to IDM. My rationale is that someday may come and some other application will need to access the contractor data and they would want access it from IDM, making IDM an HR system involuntarily. I wonder what other arguments could be made against entering contractors directly to IDM.Unknownhttps://www.blogger.com/profile/06719018463840188141noreply@blogger.com