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
This would allow usage of heimdall without additional infrastructure components, like oauth2-proxy or lua-resty-openidc in environments where the oidc protocol is "misused" in a sense, that the oidc client and the resource server/relying party build the same application and oidc is used to get information about the authenticated user only, so only the id token is relevant.
In such 1st party scenarios, an auth proxy is used to drive the authorization code grant flow if no authentication information is present in the downstream request and ensures the user is authenticated. Currently, heimdall does only support the second part (and actually goes far beyond it)
Having that functionality in place would make heimdall a full fledged identity aware proxy
This would allow usage of heimdall without additional infrastructure components, like oauth2-proxy or lua-resty-openidc in environments where the oidc protocol is "misused" in a sense, that the oidc client and the resource server/relying party build the same application and oidc is used to get information about the authenticated user only, so only the id token is relevant.
In such 1st party scenarios, an auth proxy is used to drive the authorization code grant flow if no authentication information is present in the downstream request and ensures the user is authenticated. Currently, heimdall does only support the second part (and actually goes far beyond it)
Having that functionality in place would make heimdall a full fledged identity aware proxy
Requires #97
The plan is to implement OAuth for browser-based apps.
The text was updated successfully, but these errors were encountered: