Hey @thankful-secretary-66849
Yes, this is by design. In Ory's architecture, Ory Hydra (OAuth2 provider) and Ory Kratos (identity/session management) operate independently.
Hydra's refresh token flow does not, by default, check the state of the user's Kratos session when issuing new access tokens.
As long as the Hydra refresh token is valid, it can be used to obtain new access tokens—even if the original Kratos session has expired or is no longer active.
This separation is intentional and common in OAuth2 systems: refresh token validity is managed by Hydra, and session validity is managed by Kratos.