Cookie Settings
Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Other cookies are those that are being identified and have not been classified into any category as yet.

No cookies to display.

Single Sign On

Identity Provider Versus Single-Sign-On


An identity provider (IdP) can facilitate single sign-on (SSO) by acting as a central authentication service that allows users to access multiple applications and services with a single set of login credentials. Here are the steps involved in the SSO process with an IdP (for OpenID Connect):

  1. The user logs in to the IdP: The user visits the IdP’s login page and enters their username and password. The IdP then verifies the user’s credentials and generates an authentication token.
  2. The user accesses the application or service: The user navigates to an application or service that supports SSO via the IdP.
  3. The application or service redirects the user to the IdP: When the user tries to access the application, the application detects that the user is not yet authenticated and redirects the user to the IdP with a request to authenticate.
  4. The IdP generates an access token: The IdP recognizes the user from the authentication token generated during step 1 and generates a new access token that indicates that the user is authenticated and authorised to access the application or service.
  5. The access token is sent back to the application or service: The IdP sends the access token back to the application or service.
  6. The user gains access to the application or service: The application or service recognizes the access token as valid and grants the user access to the application or service without requiring the user to enter additional login credentials.

By acting as a central authentication service, an IdP can simplify the login process for users and reduce the risk of password reuse and related security issues. It also allows organisations to more easily manage access to multiple applications and services for their users.

The next step… How to enable Single-Sign-On across multiple Identity Providers? For that, Agilicus can assist you with our unified authentication.