Active Directory managing IDs through SSO on multiple system applications
What do you like best?
We are able to create a Customer Account in Active Directory and use SSO to clone authentication to child system applications linked to our Active Directory.
What do you dislike?
Security requires various authentication checkpoints to be separated among teams and requires coordination on some types of login information changes.
Recommendations to others considering the product:
Active Directory allows us to manage security level groups and easily manage authentication to various systems. We also are able to have one security setup for our employees and another to use for external customers.
What problems are you solving with the product? What benefits have you realized?
We have made it easier to allow our Customers to self-maintain their accounts, our Helpdesk to assist in minor account resolutions, leaving our support level teams to handle the major problems to resolve. The result is faster resolutions for account issues, and our setup allows Single Sign-On (SSO) to chain authentication on multiple systems with a Parent (Active Directory) and System Application (Child) relationship system.