Scope offline vs offline_acces

The sample config in docs/config.yaml says: Scope offline, offline_access, and openid are always included.
However offline_access is not advertised in .well-known/openid-configuration after setting explicitly in supported_scope it does. Is this expected? Does the sample config need to be updated? seems to suggest that offline is an alias for offline_access but I still have to set offline_access rather than offline in the client-configuration to get a refresh token when using a standard client like

Also why is offline even supported? The OIDC spec mentions only scope offline_access.

They’re just aliases for backwards compatibility :slight_smile: