OneLogin provides a custom connector option that makes it easy to configure your OpenID Connect-enabled app to use OneLogin as the Identity Provider (IdP) in an OpenID Connect flow.

We recommend using a certified OpenId Connect client to interact with our OpenId Connect APIs. The following code samples demonstrate how to use various OpenId Client libraries.

In this flow, the device instructs the user to open a URL on a secondary device such as a smartphone or computer in order to complete the authorization. There is no communication …

The key difference between the PKCE flow and the standard Authorization Code flow is users aren’t required to provide a client_secret. PKCE reduces security risks for native apps, as …

The Authorization Code Flow is the most secure and preferred method to authenticate users via OpenId Connect. This is the first of two requests that need to be made to complete the flow.

In this flow, the device instructs the user to open a URL on a secondary device such as a smartphone or computer in order to complete the authorization. There is no communication …

The OpenId Connect Client Credentials grant can be used for machine to machine authentication. In this grant a specific user is not authorized but rather the credentials are verified and a …

Implicit Flow Use this API to authenticate a user as part of the OpenID Connect Implicit Flow and generate an ID Token for the user. While the Implicit Flow is still a valid option for Single Page …

We’ve made life easier for you with a new OpenId Connect Inspector. The Inspector is quick to configure and enables you to try out the Implicit or Authorization Code flows using your own …

Openid Connect Authentication automatically adjusts to user-based security policies, MFA requirements, and login flows you defined in OneLogin without requiring additional code.