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

Getting Started

Getting Started

Prepare your website and choose the right DocID® integration path.

Before you begin, decide which content requires DocID® and what should happen after a user signs in.

Prepare the implementation

  1. Identify the website or application that will become the DocID® asset.
  2. Define which routes, pages, downloads, or actions require authentication.
  3. Decide whether access is uniform or depends on profile attributes.
  4. Choose the Drupal module, WordPress plugin, or a custom OAuth integration.
  5. Obtain the development client configuration from your DocID® contact.
  6. Register every callback URL needed for development, staging, and production.
  7. Test the complete success, cancellation, and error journeys.

Minimum integration

A minimum implementation must:

  • Redirect unauthenticated visitors to DocID®
  • Generate and validate state
  • Use PKCE with S256
  • Exchange the returned code from server-side code
  • Create and revoke its own website session
  • Handle denied consent and protocol errors safely

Next step

Use the implementation path that matches your platform:

  • Drupal module setup
  • WordPress plugin setup
  • Custom website setup
PreviousCore conceptsNextDrupal module

On this page

  1. Prepare the implementation
  2. Minimum integration
  3. Next step