You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.
WHAT ALREADY DONE
I have one mvc app, one identity server and many webapis.
For internal users i used hybrid flow with response_type='code id_token'.
When mvc app sees [Authorize] attribute, it redirects the user to login form on identity server, then user post his credentials and cookies with id_token and access_token are sent to browser. It works good.
WHAT IS NEEDED
For external users network administrators disallow to redirect to the identity server as it is inside intranet.
I see how to bypass this problem through the following way:
When mvc app sees [Authorize] attribute, it shows login form.
When user post his credentials to this form, browser or MVC somehow passes it to IS4.
IS4 authenticates user and returns all needed cookies with tokens to access mvc and web apis.
Please tell if this is possible , or there is workaround to archive this behavior.
Thank you in advance!
The text was updated successfully, but these errors were encountered:
WHAT ALREADY DONE
I have one mvc app, one identity server and many webapis.
For internal users i used hybrid flow with response_type='code id_token'.
When mvc app sees [Authorize] attribute, it redirects the user to login form on identity server, then user post his credentials and cookies with id_token and access_token are sent to browser. It works good.
WHAT IS NEEDED
For external users network administrators disallow to redirect to the identity server as it is inside intranet.
I see how to bypass this problem through the following way:
Please tell if this is possible , or there is workaround to archive this behavior.
Thank you in advance!
The text was updated successfully, but these errors were encountered: