Master of nuggets, chicken bones and all other kinky food!

Security Engineering

Single Sign-on Methods

Many of the services that we use suggesting that we should use different password for them and we should never write it down to anywhere, in case of security. Having a different password for each system that we use force us to remember maybe more hundreds of password as we have many different accounts on many different software / websites.

“it’s arguable that SSO only reaches its full potential when you do away with that final password and

use biometrics for authentication.” (Steve, M n.d)


Single sign on technology is surely a good idea if there are lots of different logins for a user. Having one single mechanism to be able to log in or out for all those different account is obviously a we very useful idea.

global-listAccording to Microsoft’s MSDN components of SSO are (What they are talking obviously a Windows based Single sign on operation):

Mapping: With this component user’s Windows account could be attached to many different back end entry systems.

Lookup:  As an SSO runtime component, Looks up checks users login credentials across in different databases of back end systems.

Administration: Especially during mapping administration component is used very widely by Single sign on process by Microsoft.

Secret: Secret component generates the master secret and distributes it to other single sign on servers located in the system. This component is active only when the single sign on server works as the master server.

Password Synchronization: Keeps the password synchronized in users database and make it easier to be used by the system.  (MSDN, nd)


‘SSO Components ‘, (nd), ‘MSDN’, [Online] Available from viewed 14 July 2012

Steve, M n.d., ‘Feature: Single Sign-On: matching convenience with security’, Biometric Technology Today, 2011, pp. 7-11, ScienceDirect, EBSCOhost, viewed 14 July 2012.

Leave a Reply

Your email address will not be published. Required fields are marked *