Gone are the days when you force your users to register into your application by creating username/password. Everyone wants to skip that process when they can identify themselves using other ways (google, facebook, twitter…), and they want to use their single sign on process to identify them across multiple applications and multiple websites. In this post I am trying to explain the process and its technologies in simple English.
So you are a developer who is building an application and want to allow your users to use their Google credentials to authenticate themselves into your account. I am going to explain to you the concepts and the technologies.
To accomplish that, your application must make a request to some API service on the Google Account website in order to initiate the user authentication process and receive a response that identifies the user. The Google Account website is the only place where the authentication process should run, and where the user enter their credentials. And Google authentication service should ensures that the credentials are safe and hidden from our application.
The process of using an external server to sign-on and using its returning identity in different applications is called
Single Sign-On (SSO).
Google Account website stores information about the user who did previously register into Google Account website. The digital information that uniquely identifies a user on Google Account website and shared on other websites and domains is known as
The Google Account website has to provide API services that will achieve that process, and these services must use common protocols and policies that are understood by our application and Google Account. These protocols and policies are called
Federated Identity Management (FIdM).
Google Account is the provider that provides Authentication service to identify users, and return their Federated Identities, and the technical terms for it is:
Federated Identity Provider.
Our application will be the consumer or the client for
There are many different Federated Identity Providers: Google, Microsoft, Twitter, Facebook…etc. They all provide these FIdM services for industry standard protocols.
There are three technologies that provide FIdM services:
- SAML (Security Assertion Markup Language): It is the oldest technology, and although it is limited used now but still kicking around.
- OAuth 2.0: the most common one, because it is implemented by all providers.
- OpenID Connect: is it built on top of OAuth but it cut lots of extra stuff and concentrate on authentication.
SAML was the oldest one, and is used mainly for web applications and mostly internal web applications. It uses XML to communicate to the Identity providers. SAML was developed when calling external services was done using SOAP (an old protocol from web services).
Interesting to note that an approach to make better SAML was initiated and was called
WS-Federation but then later REST and HTTP replaced SOAP, and JSON replaced XML, and SAML/WS-Federation became less and less used.
SAML only returns a digital identity called
SAML Assertion to identify the user. The
SAML Assertion is very simple and it is the simplest representation of the user.
Although OAuth is used as one of FIdM technologies, but it wasn’t mainly built for that purpose. With the rising of social media and the wealth of its data, social media companies wanted to provide its data and share user data across the applications. They provided more sophisticated protocols to share user information and allow users to choose what information they want to share, and this is how OAuth 2.0 was built.
Because OAuth 2.0 needed to identify the users on their own social media servers, so it has the SSO features of FIdM, beside it added more features to allow users to chose what information they want to share.
For example on google we all saw this when using google login.
As you see that OAuth has more that SSO and FIdM, but it built very good technologies and protocols, and this is why OpenID came up to life.
Because OAuth had good technologies and standards to achieve SSO and FIdM, but has way more of Authorization and sharing information, the industry built a new standard that use OAuth technologies but concentrate only on the Authentication process and cut out the authorization, and it only share the basic data that uniquely identify the user. This new standard is OpenID Connect 1.0. OpenID Connect uses lots of common technologies with OAuth, that is sometimes it get confused.
OAuth created many workflows each work better for a specific type of applications. OAuth called these workflows:
OpenID still using these flows but slightly modified them. So understand them with OAuth is the same as OpenID.
We can define these types of applications:
- Website application that serve its own UI.
- Mobile native APP.
- Local desktop App.
Each type has its matching OAuth, and each
flowcommunicate to the
Authorization Server (SA)using different services and end point.
|the Authorization Code Flow with Proof Key for Code Exchange (PKCE)
Implicit Flow used to be the one but not any more
|Local Desktop App
|Client Credential Flow
|Native mobile APP
|the Authorization Code Flow with Proof Key for Code Exchange (PKCE)
You can build your own
SaaS services on the market.
SaaS services provides all the OAuth 2.0 and OpenID Connect services for your needs.
Just as example of these services:
- [Auth0] (https://auth0.com/) is very popular service, and maybe the most used one.
- [Google Firebase] (https://firebase.google.com/) is another very popular service.
- Microsoft Identity Platform is bunch of OAuth tools, and they are provided on Azure.
There are bunch of benefits I can list for using such services.
- Easy of use.
- Up-to-date with security standard.
By using these services, you don’t need to learn which
flow is proper for your application, and you don’t have to worry about how to implement these flow. For example if you use Auth0, and you want to implement security, Auth0 will give you a list of options for your application:
All you need to do is to chose what type of application, and by using the service with its SDK will handle the rest by choosing the proper
flow and will communicate to the server to the proper end points.
The security standard changed with time. For example: SH-256 is the accepted hash standard for encryption, but in the future that will change for sure, so by using off-the-shelf service, they will take care of that update.
Another good example is change OAuth 2.0 standard. For example the flow
Implicit Grant was an accepted standard flow for SPA application, but later in 2018 it is considered not secured enough and a new standard came which is
Authorization Code Grant. So if you were using Auth0 for example and you defined your application as SPA, all what you need to do is to update the SDK library and Auth0 will take care of the rest for you.
Hopefully I was able to explain these technical terms and technologies in simple plain English.