refined-architect-59368
12/11/2025, 11:36 AMskip_consent=True for the hydra client)refined-kangaroo-48640
12/12/2025, 5:23 PMrefined-architect-59368
12/12/2025, 5:54 PMskip_consent=True, they don't see a consent screen
⢠Therefore the OAuth flow completes, and they get logged in to Kratosrefined-kangaroo-48640
12/12/2025, 9:59 PM/oauth2/auth (Hydra) or at /login (Kratos)?
In Ory Network, you will be presented a login page (slightly different) either way.
Does your Hydra redirect to your Kratos instance (default configuration in Ory Network)?
I don't believe it is possible for the login screen to be skipped if Hydra redirects to Kratos but you have no Kratos session.refined-architect-59368
12/13/2025, 10:39 AMskip_consent=True, we don't prompt the user for consent again
Back to my question: at step 5, is it possible to always force the user to log in afresh? (e.g. by configuring Kratos to pass in the prompt=login when initiating the OAuth flow?)refined-kangaroo-48640
12/16/2025, 2:52 PMprompt=login when starting the OAuth flow unconditionally. The mechanism to achieve that is described here but requires a custom UI.
You could hack around this, provided Workspace 2 Kratos is the only OAuth client configured in Workspace 1 Hydra , by overriding the Webfinger Auth URL (https://console.ory.sh/projects/current/oauth/openid) to include ?prompt=login in Workspace 1 Hydra.refined-kangaroo-48640
12/16/2025, 2:59 PMWorkspace 2 for a given subject . Logging out of Kratos Workspace 2 would then proceed by way of an OAuth2 logout flow in Workspace 1.refined-architect-59368
12/18/2025, 11:13 AMprompt=login isn't feasible at the moment.
For now, we've opted to perform an additional Hydra logout when the Kratos logout URL is requested, since we have access to the subject.refined-architect-59368
12/18/2025, 11:14 AM