Title: Dorvis Auth
Author: dorvis
Published: <strong>26 Agoosto, 2026</strong>
Last modified: 18 Sebteembar, 2026

---

Raadi kaabayaal

![](https://ps.w.org/dorvis-auth/assets/icon-256x256.png?rev=3668402)

# Dorvis Auth

 Qore [dorvis](https://profiles.wordpress.org/dorvis/)

[Soo Rog](https://downloads.wordpress.org/plugin/dorvis-auth.0.1.2.zip)

 * [Faahfaahin](https://so.wordpress.org/plugins/dorvis-auth/#description)
 * [Dibu-eegisyo](https://so.wordpress.org/plugins/dorvis-auth/#reviews)
 *  [Rakibaad](https://so.wordpress.org/plugins/dorvis-auth/#installation)
 * [Horumarinta](https://so.wordpress.org/plugins/dorvis-auth/#developers)

 [Taageero](https://wordpress.org/support/plugin/dorvis-auth/)

## Sharraxaad

Dorvis Auth allows your WordPress users to log in using the Dorvis OIDC provider.
It supports the Authorization Code Flow with PKCE for secure authentication.

**Features:**
 * “Authenticate with Dorvis” button on the login form. * Automatic
account creation on first sign-in, or link-only mode where users attach a Dorvis
identity to an account they already have. * Maps First Name and Last Name from OIDC
claims. * Optionally rejects username and password sign-in once everyone has linked.*
Configurable Client ID, Secret, Issuer URI and Redirect URI via Settings.

### Privacy

[Dorvis Privacy and Cookie Policy](https://dorvis.eu/en/privacy)

## Rakibaad

 1. Upload the `dorvis_auth` folder to the `/wp-content/plugins/` directory.
 2. Activate the plugin through the ‘Plugins’ menu in WordPress.
 3. Go to **Settings > Dorvis Auth**.
 4. Enter your **Client ID** and **Client Secret**.
 5. Set the **Issuer URI** and the **Redirect URI** (must match your Dorvis OIDC configuration).
 6. Save changes.

The Redirect URI path must be routed to WordPress, so the site needs a permalink
structure other than Plain.

## SBI

### Where do I get my Client ID?

You must contact Dorvis support or use the demo credentials provided in the documentation.

### How do I move an existing site to Dorvis sign-in?

Turn off **Create accounts automatically**. Existing users sign in with their password,
open their profile and click **Link Dorvis identity**. The Users list shows who 
has linked. Once everyone has, turn on **Disable password sign-in**.

### Can I link accounts in bulk instead of asking everyone to click?

Turn on **Match accounts by personal code**, then set the `dorvis_personal_code`
user meta field on each account to that person’s code, digits only with no dashes
or spaces. Those users can sign in with Dorvis straight away. The Users list shows
them as Pending until they first sign in, so a mistyped code is visible before anyone
is locked out.

Accounts that were already linked before the setting was turned on keep working,
and their personal code is filled in the next time they sign in.

    ```
    dorvis_personal_code is the only user meta field meant to be written by hand. Setting `dorvis_sub` directly also links an account, but the plugin then treats it as one it created and overwrites its name and public URL slug from Dorvis on the next sign-in.
    ```

### What if Dorvis is unreachable and password sign-in is disabled?

Define `DORVIS_AUTH_ALLOW_PASSWORD_LOGIN` as true in `wp-config.php`.

### Does this work alongside a two-factor authentication plugin?

No. Signing in with Dorvis establishes the WordPress session directly, so plugins
that add a second factor to the username and password form are not part of that 
path. The second factor is whatever the Dorvis identity provider asks for.

### What claims are mapped?

given_name and `family_name` become the user’s name fields and display name, and
the name also becomes the public URL slug. `person_code` is stored as the `dorvis_personal_code`
user meta field; it is never used as the username.

This mapping is applied on every sign-in to accounts the plugin created. An account
that already existed on the site when it was linked keeps the name and public URL
slug the site gave it.

## Dibu-eegisyo

Ma jiraan wax dibu-eegis ah oo ku saabsan kaabahan.

## Ka-qaybgalayaasha & Horumariyayaasha

“Dorvis Auth” waa softiweer il furan. Dadka soo socda ayaa wax ku biiriyay kaabahan.

Ka-qaybgalayaasha

 *   [ dorvis ](https://profiles.wordpress.org/dorvis/)

[Ku tarjun “Dorvis Auth” luqaddaada.](https://translate.wordpress.org/projects/wp-plugins/dorvis-auth)

### Ma xiisaynaysaa horumarinta?

[Baadh koodka](https://plugins.trac.wordpress.org/browser/dorvis-auth/), fiiri [bakhaarka SVN](https://plugins.svn.wordpress.org/dorvis-auth/),
ama iska qor [diiwaanka horumarinta](https://plugins.trac.wordpress.org/log/dorvis-auth/)
adigoo adeegsanaya [RSS](https://plugins.trac.wordpress.org/log/dorvis-auth/?limit=100&mode=stop_on_copy&format=rss).

## Isbeddellada

#### 0.3.0

 * Added link-only mode and a link/unlink control on the user profile screen. Unlinking
   your own identity requires a password sign-in, so it cannot lock you out; an 
   administrator can unlink another account either way.
 * Added an option to reject password and application password sign-in, with a `
   wp-config.php` escape hatch.
 * Added a “Dorvis” column to the Users list.
 * Added an option to identify accounts by personal code, which allows linking them
   in bulk. Off by default; while it is off the personal code is neither stored 
   nor matched on.
 * The ID token is validated and discarded rather than kept in user meta. Signing
   out clears the WordPress session, which is all there is to clear.
 * The `personal_code` user meta field written by 0.2.0 is renamed to `dorvis_personal_code`
   on upgrade, so it is read again and removed on uninstall rather than left behind.
 * Deleting the plugin now removes its settings, the user meta it wrote and its 
   cached discovery data.

#### 0.2.0

 * Account usernames and profile URL slugs are now derived from the OIDC subject
   and the name claims.
 * Discovery documents are cached per issuer, signing keys are cached and refreshed
   when validation fails, and token endpoint errors are surfaced to the user.
 * The Issuer URI must now use https.

#### 0.1.0

 * Added PKCE, state and nonce protection to the authorization request.
 * Added callback handling with state verification.
 * Added ID token validation, discovery caching and logout.

#### 0.0.2

 * Added settings page.
 * Improved user mapping logic.

#### 0.0.1

 * Initial release.

## Meta

 *  Version **0.1.2**
 *  Last updated **11 saac kahor**
 *  Active installations **In ka yar 10**
 *  WordPress version ** 5.5 ama ka sareeya **
 *  Tested up to **7.1.1**
 *  PHP version ** 8.0 ama ka sareeya **
 *  Language
 * [English (US)](https://wordpress.org/plugins/dorvis-auth/)
 * Tags
 * [authentication](https://so.wordpress.org/plugins/tags/authentication/)[login](https://so.wordpress.org/plugins/tags/login/)
   [oidc](https://so.wordpress.org/plugins/tags/oidc/)[openid connect](https://so.wordpress.org/plugins/tags/openid-connect/)
   [sso](https://so.wordpress.org/plugins/tags/sso/)
 *  [Aragti Sare](https://so.wordpress.org/plugins/dorvis-auth/advanced/)

## Qiimeynta

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/dorvis-auth/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/dorvis-auth/reviews/)

## Ka-qaybgalayaasha

 *   [ dorvis ](https://profiles.wordpress.org/dorvis/)

## Taageero

Ma heysaa waxaad dhahdo? Caawimaad ma u baahan tahay?

 [Eeg madasha taageerada](https://wordpress.org/support/plugin/dorvis-auth/)