File tree Expand file tree Collapse file tree 3 files changed +3
-4
lines changed Expand file tree Collapse file tree 3 files changed +3
-4
lines changed Original file line number Diff line number Diff line change @@ -282,7 +282,7 @@ troubleshoot:
282
282
1 . Review the logs. Search for the term ` notifications ` for diagnostic information.
283
283
284
284
- If you do not see any relevant logs, set
285
- ` CODER_VERBOSE=true ` or ` --verbose ` to output debug logs.
285
+ ` CODER_LOG_FILTER=".*notifications.*" ` to filter for notification-related logs.
286
286
1 . If you are on version 2.15.x, notifications must be enabled using the
287
287
` notifications `
288
288
[ experiment] ( ../../../install/releases/feature-stages.md#early-access-features ) .
Original file line number Diff line number Diff line change @@ -203,7 +203,7 @@ Visit the Coder UI to confirm these changes:
203
203
# ## Group allowlist
204
204
205
205
You can limit which groups from your identity provider can log in to Coder with
206
- [CODER_OIDC_ALLOWED_GROUPS](https://coder.com/docs /cli/server#--oidc-allowed-groups).
206
+ [CODER_OIDC_ALLOWED_GROUPS](../../reference /cli/server.md #--oidc-allowed-groups).
207
207
Users who are not in a matching group will see the following error:
208
208
209
209
< Image height=" 412px" src=" ../../images/admin/group-allowlist.png" alt=" Unauthorized group error" align=" center" />
@@ -419,7 +419,6 @@ If you are running into issues with a sync:
419
419
1. To reduce noise, you can filter for only logs related to group/role sync:
420
420
421
421
```sh
422
- CODER_VERBOSE=true
423
422
CODER_LOG_FILTER=".*userauth.*|.*groups returned.*"
424
423
```
425
424
Original file line number Diff line number Diff line change @@ -27,7 +27,7 @@ claims from the ID token and the claims obtained from hitting the upstream
27
27
provider's ` userinfo ` endpoint, and use the resulting data as a basis for
28
28
creating a new user or looking up an existing user.
29
29
30
- To troubleshoot claims, set ` CODER_VERBOSE=true ` and follow the logs while
30
+ To troubleshoot claims, set ` CODER_LOG_FILTER=".*got oidc claims.*" ` and follow the logs while
31
31
signing in via OIDC as a new user. Coder will log the claim fields returned by
32
32
the upstream identity provider in a message containing the string
33
33
` got oidc claims ` , as well as the user info returned.
You can’t perform that action at this time.
0 commit comments