History Of SAML

629 Words2 Pages

What is SAML?
SAML is an abbreviation of Security Assertion Markup Language, which is an XML based standard for web browser Single Sign On (SSO), and defined by OASIS. It is in rife since 2002. SAML is called a security markup language because this is specifically defined to exchange security and identity related information such as authorization information and authentication information etc.
Background
Its first version came in 2002 as SAML 1.0 and the latest version released in 2005 as SAML 2.0. Another version came in between as SAML 1.1.
Why SAML!
In view of emergence in cloud computing and cloud based identity management providers, the need for implementing SAML protocol is imperative. In addition, with the proliferation of SaaS (Software as a Service), and other web based applications, identity management has become challenging for various enterprises. Handling so many usernames and passwords for your intranet, cloud, webmail, HR system, and other resources is nothing but bothersome especially when your workforce is huge. This is where SAML is desperately needed. Many hosted services providers support SAML for authentication including Google Apps, Salesforce.com, Zendesk and Zoho. Thousands of large enterprises have adopted it as their standard protocol for their communicating identities across their network environments.

How SAML works!
SAML generally defines three roles i.e. the principal (which is normally an end user), the identity provider (IdP), and the service provider (SP). A system that supports SAML as a means for authentication is referred to as a Service Provider (SP). An SP requires the availability of an Identity Provider (IdP).
Let’s consider Google Apps with SAML configured for instance. Google Apps d...

... middle of paper ...

...ord. With one time login they can access to all resources or systems for rest of the day.
• Security — Due to common password security policies which are centrally managed, SAML is secured. No need for users to jot down their passwords when there is only one to remember.
• Cloud Computing — SAML reduces the complexity of end users who access multiple cloud applications. It allows the user to remember only one password, and if required, use as strong authentication credential just once to securely access all cloud applications.
• Speed — Single browser redirect is all it takes to securely sign a user into an application.
• Minimizes Help desk calls — Reduction of help desk calls for password resets.
• Bring your own Device — where there is increased use of Bring your own Device (BYOD), SAML best fits since multiple accounts can be accessed from anywhere, any time.

Open Document