Who uses SAML 2.0 authentication protocol

In our blog, we often touch upon issues of data protection and authorization. For example, we talked about the new WebAuthn passwordless authorization standard and even interviewed one of its developers. Also discussed was DANE technology for DNS domain name authentication. Today we’ll talk about the SAML 2.0 protocol and those who use it.

Photos - Marco Verch - CC BY - Photo modified

What is SAML

SAML is an XML-based markup language that underlies Single Sign-On (SSO) technology. It gives users the ability to switch between applications (for example, corporate) with a single login / password pair.

Using the SAML protocol, account providers (IdP, or identity provider) and service providers (SP, or service provider) interact with each other to securely transfer the identity of application users. The role of an account provider can be played by the Active Directory directory service and even a simple SQL database with logins and passwords. A service provider can be any web application in which a user wants to log in (of course, supporting SAML).

In general, the authentication process consists of the following steps:

  1. The user asks to authorize it in the application from SP.
  2. The service provider requests a login confirmation from IdP.
  3. The account provider sends a special SAML message in which it says that the credentials are correct or incorrect.
  4. If the data is correct, the provider will authorize the user.

Who implements it

The latest major update to SAML, SAML 2.0, was published in 2005. And since then, the protocol has become quite widespread. It is supported by services such as Salesforce , Slack, and GitHub . It is even used by the ESIA information system for authorization on State services.

It would seem that in such a long time the protocol should have become something mundane, but recently it has been raising interest again - a large number of articles have been published on the topic ( here and there ), and there is an active discussion on social networks. SAML was also launched by IaaS providers.

For example, a month ago, SAML introduced the Azure Active Directory Proxy Service, a tool for gaining remote access to web applications. According to some experts, the service development company decided to use this protocol, since it provides more reliable SSO login protection for large companies than alternatives like OAuth.

In late July, it also became known that SAML appeared in the AWS cloud. The company hopes that this way customers will spend less time on authorization and will be able to focus on solving business critical problems.

Not only cloud providers, but also non-profit organizations pay attention to the protocol. A couple of weeks ago, the Public Safety Technology Alliance (PSTA), which promotes technology for public safety, recommended its partners implement authorization based on SAML 2.0 and OpenID. Among the reasons were highlighted: the maturity of technologies, their prevalence and reliability.

Protocol Opinions

First of all, SAML-based solution integrators note that the protocol simplifies the work of system administrators in large companies. They do not have to keep track of dozens of passwords for different corporate applications for each employee. It is enough for the administrator to assign each employee only one unique username / password pair for single sign-on to all services. This approach provides another advantage: if an employee leaves the company, it is enough to cancel his identification data for single sign-on. But there are also negative sides.

Photo - Matthew Brodeur - Unsplash

For example, among the shortcomings highlight excessive complexity. SAML is built on the basis of XML, so it is syntax-intensive. Plus, the protocol has a large number of optional components, which greatly complicates the configuration of SSO.

Although security experts consider the SAML protocol to be fairly reliable, there are concerns about vulnerabilities in hotel libraries for SSO operations. Last year, security engineers at Duo Labs found an XML comment processing bug. By modifying the username field in a SAML message, an attacker can impersonate another user. However, an important condition for carrying out an attack is having an account on the victim’s network.

In any case, this vulnerability can be mitigated (for example, use a white list of mail addresses and domains for registration on the network), so it should not affect the further spread of technology among IT companies and cloud providers.

What we write about in our blogs and social networks:

New open source licenses
The Open Invention Network has more than three thousand licensees - what does it mean for open source software

How to protect a virtual server on the Internet
How to save using API

Digest: 5 books and one course on networks
A selection of books for those already engaged in system administration or planning to start

We at 1cloud.ru offer the service “ Cloud Object Storage ”. It allows you to store backups and work with archive data.

Source: https://habr.com/ru/post/463775/

All Articles