This page describes several use cases in which OpenID Connect may be used.

Different Identity Provider

There exist a plethora of identity providers. Some frequently used are LDAP or Kerberos. In case your company wants to use a different identity provider, then the OpenID Connect feature adds a large lists of identity providers to the possiblities. As OpenID Connect is a standard, each identity provider which follows this standard now or in the future can be used. For example when starting a flow with roles on it, the user could use his/her facebook credentials to log on.

Single Sign On

The term Single Sign On is one you might have heard of. This essentially means that once you are logged in one system, you are authomatically logged in to all systems and you do not have to provide your username or password over an over again for each system you want to use. How this technically works is explained in more detail on the other pages in this guide. The simple explanation is that you get a token when you log in for the first system. As long as you have this token and send it for any other request after that, you do not need to log in again.

Blueriq Within a Portal

Blueriq often is part of a bigger page. It for example displays a widget inside a portal page. The end user needs to log on to the portal page to start his/her work. As you want to secure the Blueriq widget with a role, it would be inconvenient to log in a second time for the widget, specially as the end user just had logged in into the portal. When a Blueriq application receives an OpenID Connect token, it will validate the token and not ask the user to log in again in case that it is valid.