DocID®DocID® Documentation
Back to DocID®
  • Overview

    • DocID® Documentation
  • Introduction

    • Introduction
    • How DocID® works
    • Core concepts
  • Getting Started

    • Getting Started
    • Drupal module
    • WordPress plugin
    • Custom website
    • Go-live checklist
  • Features

    • Features
    • Standard Login
    • Access and personalization
    • Analytics
    • Campaigns
  • Licenses

    • Licenses
  • OAuth 2.0

    • OAuth 2.0
    • Configure a client
    • Authorization code flow
    • Scopes and UserInfo
    • Security and environments
  • API

    • API
  • Help

    • Troubleshooting

OAuth 2.0

OAuth 2.0

Integrate DocID® with the authorization code flow and PKCE.

DocID® custom website integrations use the OAuth 2.0 authorization code flow with PKCE. OpenID Connect scopes provide the authenticated user's approved identity claims.

Endpoints

PurposeURL
Authorizationhttps://docid.pro/oauth2/authorize
Token exchange and refreshhttps://docid.pro/oauth2/token
User informationhttps://docid.pro/oauth2/userinfo
Token introspectionhttps://docid.pro/oauth2/introspect
Token revocationhttps://docid.pro/oauth2/revoke

These are the production endpoints. For another environment, use the issuer and client configuration supplied for the asset instead of guessing the host.

Implementation sequence

  1. Configure the client.
  2. Implement the authorization code flow.
  3. Request only the needed scopes and claims.
  4. Apply the security and environment guidance.

The OAuth endpoints implement the login protocol. The business API is a separate interface for supported application resources.

PreviousLicensesNextConfigure a client

On this page

  1. Endpoints
  2. Implementation sequence