Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
SAML is a standard way to pass your company login to another service. Its full name is Security Assertion Markup Language, and the standards body OASIS defines it. What it passes is not the password itself but a notice that works like a certificate saying "this person has been confirmed".
How does SAML work?
Think of showing a letter of introduction, issued by your own company, at the reception desk of a business partner's building. The reception trusts the company that issued it, so it lets you in without checking who you are all over again.
In SAML, the side that handles identity checking (the IdP) creates a notice, called an assertion, that records the result of the check and attributes such as an email address. The service you use (the SP) receives it. OASIS's technical overview explains the design in terms of parts called assertions, protocols, bindings, and profiles.
The notice can carry an electronic signature so that tampering can be seen, and the service accepts it after verifying the signature. OWASP's SAML cheat sheet collects cautions for avoiding implementation mistakes, such as how to verify signatures. The overall picture of single sign-on and measures against improper login are collected under unauthorized access measures. The free URL check sees only what is public, so how signatures are verified in your SAML setup is for a consultation.
Why does SAML matter?
When a company uses many cloud services, creating and managing an ID for each service takes growing effort. With services that support SAML, you can gather the login into your company's own mechanism.
If the implementation has a mistake, someone may be able to log in by pretending to be another person. So you do not build it yourself: you use a proven library or product and check the settings.
Checking the recipient and the expiry of the notice is also the service side's job. After introduction, when you change a setting, try a real login to confirm it.
Related terms
- Single sign-on (SSO): one login lets you use many services
- OpenID Connect: another standard way to log in with the ID of another service
- OAuth: a method for granting permission without handing over the password
- Multi-factor authentication: a mechanism that firms up the identity check at the SAML entrance
Next step
List which of the services you use support linking through SAML. You can check this in the service's admin screen or its help pages. The free URL check shows only what is visible from outside, and we take questions on designing the link in a free consultation.
Frequently asked questions
How do SAML and OpenID Connect differ?
Both are standards for telling another service the result of a login. SAML uses a notice in XML format. OpenID Connect is built on OAuth and conveys the result in an ID token in JSON format (a JWT).
Does the password go to the service in a SAML login?
It does not. What is sent to the service is a notice showing that the identity check is complete, and the password stays with the side that handles the check.
Frequently asked questions
How do SAML and OpenID Connect differ?
Both are standards for telling another service the result of a login. SAML uses a notice in XML format. OpenID Connect is built on OAuth and conveys the result in an ID token in JSON format (a JWT).
Does the password go to the service in a SAML login?
It does not. What is sent to the service is a notice showing that the identity check is complete, and the password stays with the side that handles the check.