Skip to content

Commit 094482e

Browse files
authored
Merge pull request #59 from Hutch79/patch-1
Added Property Mapping configuration for AUthentik OIDC Setup
2 parents 0830fdd + 70db192 commit 094482e

2 files changed

Lines changed: 25 additions & 1 deletion

File tree

docs/OIDC-Guides/OIDC-Setup-With-Authentik.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,31 @@ Before setting up a provider and app, ensure that Authentik is installed and run
2626

2727
![Authentik user dashboard](../resources/authentik/1-user-dashboard.png)
2828

29-
### Step 2: Create a Provider
29+
### Step 2: Create a Property Mapping
30+
31+
In version 2025.10 Authentik changed their default value for the `email_verified` field from true to false.
32+
Since RomM requires a verified email address, without this property, the authentication would fail.
33+
34+
1. **Navigate to Property Mappings**
35+
- Go to the "Property Mappings" section in the Authentik admin interface `Customization > Property Mappings`
36+
2. **Create a new Property Mapping**
37+
- Select "Scope Mapping"
38+
- Enter a Name like "RomM Email Verification"
39+
- Set `email` as scope name.
40+
- Set the following as the expression:
41+
```py
42+
return {
43+
"email": user.email,
44+
"email_verified": True,
45+
}
46+
```
47+
- It should look like this
48+
![Propperty Mapping](../resources/authentik/propperty-mapping.png)
49+
3. **Click Create**.
50+
51+
[Authentik docs reference](https://version-2025-10.goauthentik.io/add-secure-apps/providers/property-mappings/#scope-mappings-with-oauth2)
52+
53+
### Step 3: Create a Provider
3054

3155
A provider in Authentik acts as the bridge between RomM and Authentik.
3256

46.1 KB
Loading

0 commit comments

Comments
 (0)