How does your work manage their user accounts? [modified]
-
Hi, I'm kinda curious how the other here deal with managing user accounts across different systems. Heres why I'm asking: We have several 3rd party web applications that when a user is hired need to have access to. Depending on there department and position they may or may not have access to those systems. (So it's not a "they have it or they don't" situation) Setting up a user to these systems is easy as the hiring manager usually issues the request of what systems the new hire needs. THE PROBLEM is that when a user quits/terminated/leaves there is no real checklist for what systems needs to be removed. Now that where going though our IT Audit, I've noticed we have some old accounts that exist in some applications.:confused: Most of these applications belong to 3rd party companies but since we (my department) is IT were responsible for setting them up. I'm kinda of curious what others in the industry do. The developer in me already wanted to suggest building a application that just manages what applications users have access to. But I know thats just me wanting to do some asp.net coding :-D Curious what you guys think... Thnx, Rick -- modified at 11:28 Thursday 22nd March, 2007
-
Hi, I'm kinda curious how the other here deal with managing user accounts across different systems. Heres why I'm asking: We have several 3rd party web applications that when a user is hired need to have access to. Depending on there department and position they may or may not have access to those systems. (So it's not a "they have it or they don't" situation) Setting up a user to these systems is easy as the hiring manager usually issues the request of what systems the new hire needs. THE PROBLEM is that when a user quits/terminated/leaves there is no real checklist for what systems needs to be removed. Now that where going though our IT Audit, I've noticed we have some old accounts that exist in some applications.:confused: Most of these applications belong to 3rd party companies but since we (my department) is IT were responsible for setting them up. I'm kinda of curious what others in the industry do. The developer in me already wanted to suggest building a application that just manages what applications users have access to. But I know thats just me wanting to do some asp.net coding :-D Curious what you guys think... Thnx, Rick -- modified at 11:28 Thursday 22nd March, 2007
We have a central role management system - a cut down version of which we let our clients have. ALL access to our systems is controlled from this one point, and it makes adding role membership to new applications really trivial. The system includes workflow processes to add/authorise users, to add/approve roles, add users to roles and so on. We've spent a long time honing this application to the point where integrating it into applications is a simple matter of adding a couple of references, dropping in a couple of lines of code and that's it. BTW - it works for ASP.NET and WinForms.
Deja View - the feeling that you've seen this post before.
-
We have a central role management system - a cut down version of which we let our clients have. ALL access to our systems is controlled from this one point, and it makes adding role membership to new applications really trivial. The system includes workflow processes to add/authorise users, to add/approve roles, add users to roles and so on. We've spent a long time honing this application to the point where integrating it into applications is a simple matter of adding a couple of references, dropping in a couple of lines of code and that's it. BTW - it works for ASP.NET and WinForms.
Deja View - the feeling that you've seen this post before.
-
Pete O`Hanlon wrote:
We have a central role management system
Is it an off the shelf app or in house?
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
It's a one that we started to develop for our clients, and it grew from there. It evolved to the point where we can plug in additional modules as we see fit for new clients. They get the core and we drop in any additional items that are necessary.
Deja View - the feeling that you've seen this post before.