DocID

DocID® connects Drupal websites with DocID® authentication. Visitors can sign in with their existing account, while Drupal creates or links a native user account and assigns roles based on verified identity information.

For site administrators, this means that Drupal roles and permissions can be used to control access to content for verified users, professions, disciplines, institutions, or other configured groups. The module works with Drupal's existing users, roles, nodes, permissions, sessions, and media rather than introducing a separate account system.

Features

• Sign in using DocID® through OAuth 2.0.
• Automatically create or connect native Drupal user accounts.
• Map verified identity information to Drupal roles.
• Configure role mappings for professions, disciplines, institutions, subjects, or all authenticated DocID® users.
• Synchronize managed roles when a user signs in without replacing unrelated roles assigned by Drupal administrators.
• Restrict nodes to all authenticated DocID® users or selected Drupal roles.
• Protect files belonging to private Drupal media entities.
• Send users to different pages after authentication based on their profession or discipline.
• Provide configurable sign-in and account blocks.
• Provide a dedicated /docid/login sign-in route.
• Optionally display conditional content using supported text-filter shortcodes.
• Use Drupal's native permissions, access APIs, sessions, and cache contexts.

The module is useful for websites that provide targeted or protected information to verified healthcare professionals while continuing to use Drupal's standard user and access-management system.

Post-Installation

After installing and enabling the module:

1. Go to Configuration > People > DocID®.
2. Copy the callback URL shown on the settings page.
3. Add this callback URL as an allowed redirect URI for your website asset in the DocID® business dashboard.
4. Enter the client ID and client secret issued for the website asset.
5. Configure the Drupal roles that should be assigned for matching professions, disciplines, institutions, or subjects.
6. Review Drupal's permissions page and grant the required permissions to the mapped roles.
7. Place the provided sign-in block, or link visitors directly to /docid/login.
8. Optionally configure post-login destinations and protect individual nodes or private media.
9. Test the complete sign-in and sign-out process with a non-administrator account.

The module does not create a new content type. It adds authentication and access settings to Drupal's existing user, role, content, and media systems.

For production websites, HTTPS should be enabled. The client secret should be stored securely and may be supplied through the site's environment-specific Drupal configuration.

Additional Requirements

• Drupal 10.3 or later, or Drupal 11.
• PHP 8.1 or later.
• A DocID® account with a configured website asset.
• OAuth client credentials issued for that website asset.
• Network access from the Drupal website to the public DocID® authentication and reference-data services.
• The Drupal core File, Filter, Node, Options, and User modules.

No additional third-party PHP library or contributed Drupal module is required.

Recommended modules/libraries

• Drupal core Media: Recommended when access-controlled private media and files are required.
• Drush: Optional, but useful for installing the module, rebuilding caches, and managing Drupal from the command line.

Supporting this Module

You can support development by:

• Reporting reproducible bugs in the Drupal.org issue queue.
• Suggesting improvements and new use cases.
• Testing development releases with supported Drupal versions.
• Reviewing documentation and contributing merge requests.

For implementation or commercial support, contact [email protected].

Community Documentation

• DocID® documentation
• Drupal.org issue queue
• Module source code

Please use the Drupal.org issue queue for module-specific questions, bug reports, compatibility reports, and feature requests.