Typically, the OpenIDConnect server functions as follows:
- Visit
a.com/secure-resource
- Receive a
302
response from the server - Your browser redirects you to the identity server
- Login on the identity server
- Redirected back to
a.com
via aPOST
request - You are now logged in on
a.com
and receive access toa.com/secure-resource
in your browser.
However, I have encountered a scenario that poses a challenge which requires assistance.
- The user is already authenticated on idServer
- User is logged in on
a.com
- User is NOT logged in on
b.com
- An ajax call needs to be sent to web server
b.com
(from a different domaina.com
) b.com
uses OpenIDConnect for authentication- Due to the Ajax request to
b.com
, the standard redirection to idServer cannot occur. Instead, only a302
is received in response.
We could potentially handle the 302
response via Ajax, however, there are security concerns regarding this approach.
Nevertheless
Are there any specific scenarios within IdentityServer/OpenIDConnect meant to address these types of situations?