Single Sign on

Single sign-on is a mechanism used to enable user(s) gain access to multiple applications by logging into a system once as against multiple times. When a user signs on the login information’s authentication is propagated to all the required applications. Then the user role is used to gain access to the application. For example, say a user needs access to front end application, back end database and messaging service. If single sign-on is implemented when the user logs in he/she will be able to access all three resources. Also, with a single click of the button the user will be disconnected from all three resources automatically. The importance of this mechanism is enormous, it includes convenience, time saving, increase productivity and it enhances user and application security.

Single sign-on enables the user to create and memorize a single username and password. The odd of making errors while trying to remember this login information is reduced to minimum. Once the user logs into the system he will be able to access all the resources that is needs. Also, the user will not be bothered about the fact that when he logs out he will automatically be logged out of all resources or applications. This has happened to me because at my company we do not have the single sign-on mechanism yet. At the end of the day on Friday while I am rushing home and I log out of the applications I was using to do my job. I suddenly remember that I did not log out of all the resources I was using. Sometimes I turn around and drive one hour back to work to go double check. The convenience of this mechanism can not be over emphasized.

This mechanism saves the user time to create and remember multiple login information. The time to create and remember new login information is reduced to a minimum particularly when the login information expires. As a result of multiple sign-on users tend to get the login information mixed up resulting in messing up the whole flow.

The user does a lot...