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
So, there are a few caveats with auth_request. webauthn_proxy wants to manipulate cookies (mainly expiration) in HandleAuth, which isn't going to be respected until you add the following to your location:
Then, the next issue is error_page 401 = /webauthn/login?redirect_url=$uri;. This form causes nginx to do an internal redirect, i.e. replacing the content at $uri with the login page, overriding the headers including cookies HandleAuth wants to clear and results in redirect indefinitely. Further, if there is any space in $uri, it causes the Go http server (not nginx) to throw a 400 bad request response. These can be fixed by:
which forces nginx to do an external redirect and HandleLogin will actually see redirect_url (yes, it was not doing anything)
I caught these issues by setting hardTimeout < softTimeout. Yes, I know it is an invalid case, yet I believe making ExpireWebauthnSession work in HandleAuth does have some value.
The text was updated successfully, but these errors were encountered:
So, there are a few caveats with
auth_request
. webauthn_proxy wants to manipulate cookies (mainly expiration) inHandleAuth
, which isn't going to be respected until you add the following to yourlocation
:Then, the next issue is
error_page 401 = /webauthn/login?redirect_url=$uri;
. This form causes nginx to do an internal redirect, i.e. replacing the content at$uri
with the login page, overriding the headers including cookiesHandleAuth
wants to clear and results in redirect indefinitely. Further, if there is any space in$uri
, it causes the Go http server (not nginx) to throw a 400 bad request response. These can be fixed by:which forces nginx to do an external redirect and
HandleLogin
will actually seeredirect_url
(yes, it was not doing anything)I caught these issues by setting hardTimeout < softTimeout. Yes, I know it is an invalid case, yet I believe making
ExpireWebauthnSession
work inHandleAuth
does have some value.The text was updated successfully, but these errors were encountered: