For users that are already authenticated in identity, /oauth/authorize will always return a code for the currently logged in identity user. I'm working on a scenario (heroku/dashboard-v6#2213) where we'd want to allow users to login to other accounts without completely logging out of identity.
OpenId Connect supports use of a prompt parameter here. When that parameter is login, the user is always prompted for credentials. I know we're not implementing connect, but this seemed like a reasonable and idiomatic solution.
So, with this PR, client apps can add prompt=login to the authorize request, which will force an email/password prompt.
For users that are already authenticated in identity, /oauth/authorize will always return a code for the currently logged in identity user. I'm working on a scenario (heroku/dashboard-v6#2213) where we'd want to allow users to login to other accounts without completely logging out of identity.
OpenId Connect supports use of a
prompt
parameter here. When that parameter islogin
, the user is always prompted for credentials. I know we're not implementing connect, but this seemed like a reasonable and idiomatic solution.So, with this PR, client apps can add
prompt=login
to the authorize request, which will force an email/password prompt.