You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- This service searches for users by their **primary email** only
151
151
- Linked/alternate email addresses are **not** supported for lookup
152
-
- The service works with both Auth0 and mock repositories based on configuration
152
+
- The service works with Auth0, Authelia, and mock repositories based on configuration
153
153
- The returned subject identifier is the canonical user identifier used throughout the system
154
+
- For Authelia-specific SUB identifier details and how they are populated, see: [`internal/infrastructure/authelia/README.md`](internal/infrastructure/authelia/README.md)
Copy file name to clipboardExpand all lines: internal/infrastructure/authelia/README.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,6 +102,35 @@ The Authelia integration requires the following configuration parameters:
102
102
- NATS server connection details (inherited from main service configuration)
103
103
- Key-Value bucket configuration for user data storage
104
104
105
+
## Subject Identifier (SUB) Management
106
+
107
+
### SUB Generation and Persistence
108
+
109
+
The Subject Identifier (SUB) in Authelia is a deterministic UUID that uniquely identifies each user within the system. Key characteristics:
110
+
111
+
-**Deterministic Generation**: The SUB is a UUID that is consistently generated for each user by Authelia
112
+
-**Token-Based Persistence**: To ensure consistent data retrieval from Authelia, the SUB is only persisted when a user is updated using a valid authentication token
113
+
-**OIDC UserInfo Endpoint**: The SUB can be retrieved from Authelia's OIDC UserInfo endpoint at `/api/oidc/userinfo` using a valid token
114
+
115
+
### Token-Based User Updates
116
+
117
+
When updating user metadata through the auth service, the SUB is populated by accessing Authelia's UserInfo endpoint with the provided token:
118
+
119
+
```bash
120
+
# Example: Update user metadata with token (this populates the SUB)
0 commit comments