SAML stands for Security Assertion Markup Language. It is an XML-based open-standard for transferring identity data between two parties: an identity provider (IdP) and a service provider (SP).
SAML basically asks as a link between the authentication of a user’s identity and the authorization to use a service.
SAML, created by OASIS, remains the dominant standard among the various standards existing in the world of Federated Identity Management. The common goal among these standards is to enrich the user experience and enhance security.
SAML enables web browser SSO by allowing users to sign in to apps/services with a single set of credentials. This centralization not only provides convenience to employees but also improves organizational security, among other benefits.
One of the bigger challenges in the tech world is make sure that applications, products,Saas/PaaS solutions, cloud solutions etc built by different vendors and companies for different purposes, they work together seamlessly as a Unit. This is known as Interoperability, it refers to the ability of apps, equipment, products, and systems from different companies(vendors) to seamlessly communicate and process data in a way that does not require any involvement from end-users.
So SAML is an interoperable standard — it is a widely accepted way to communicate a user’s identity to different service providers.
SAML does two key functions:
As per wikipedia: “The SAML specification defines three roles: the principal (typically a human user), the identity provider (IdP) and the service provider (SP).In the primary use case addressed by SAML, the principal requests a service from the service provider. The service provider requests and obtains an authentication assertion from the identity provider. On the basis of this assertion, the service provider can make an access control decision, that is, it can decide whether to perform the service for the connected principal.”
With SAML SSO, the users do not log into the applications directly. Instead, they log into an SSO based platform. When a user himself authenticates successfully, SAML gives that user access to multiple resources across multiple domains.
SAML assertions are noting but XML documents sent from an IdP to an SP which identify users, and contain pertinent dat about them, and specify their privileges in the target application or service.
There are three types of SAML assertions:
Even though SAML was designed keeping in mind a wide range of use cases , but the most common one in practice is Single-sign-on(SSO). SSO, as the name implies, allows a user to log in once and then access multiple services — websites, cloud solutions or SaaS apps and so on. In an SSO scenario, all these services outsource their authentication and authorization functionality to a single system that then sends identity information about the user to those services.
SAML Single Sign-On is a mechanism that leverages SAML allowing authenticated users to log on to multiple web applications and systems, after logging into the identity provider. As the user only has to log in once, SAML SSO provides a faster, seamless user experience.
