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

Introduction

Core concepts

Learn the DocID® terms used throughout the implementation.

Asset

An asset represents a website or application using DocID®. Its configuration contains the OAuth client and the settings that control the integration.

Environment

DocID® separates development, staging, and production. Each environment has its own client credentials and registered redirect URLs. Credentials and authorization codes are not interchangeable between environments.

Client

The OAuth client identifies your website to DocID®. A confidential web client has a client ID and client secret. The secret must only be used from trusted server-side code.

Redirect URI

The redirect URI is the callback on your website. It must match a registered URI exactly, including scheme, host, port, path, query string, and trailing slash.

Scope

A scope describes the category of identity information requested by your website. DocID® currently supports openid, profile, and email.

Claim

A claim is one profile field returned for an approved scope—for example sub, email, or profession_id. Treat sub as the stable DocID® identifier for your local account mapping.

PreviousHow DocID® worksNextGetting Started

On this page

  1. Asset
  2. Environment
  3. Client
  4. Redirect URI
  5. Scope
  6. Claim