Skip to content

Explain jwks cache invalidation in the README #1225

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
julien-nc merged 1 commit into from
Oct 15, 2025
Merged

Explain jwks cache invalidation in the README #1225

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,19 @@ To skip the confirmation, use `--force`.
***Warning***: be careful with the deletion of a provider because in some setup, this invalidates access to all
NextCloud accounts associated with this provider.

#### JWKS cache invalidation

A provider-specific JWKS cache is stored by user_oidc. This cache is valid for one hour.
If the JWKS changed on the IdP side, you can clear this JWKS
cache by editing the provider with occ. You don't have to change any value. For example, if your provider identifier is
`my_identifier` and the client ID is `my_client_id`, you can run:

```
occ user_oidc:provider my_identifier --clientid my_client_id
```

to clear the JWKS cache of the provider `my_identifier`.

#### Avatar support

The avatar attribute on your IdP side may contain a URL pointing to an image file or directly a base64 encoded image.
Expand Down
Loading