Replies: 1 comment 5 replies
-
what is the version of the module that you are using? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I am using mod_auth_openidc in a reverse proxy to secure the homeassistant web-frontend.
Unfortunately, after the oidc session expired, the web-interface currently doesn't correctly re-authenticate and gets a
400 Bad request
due to expired state cookies.I investigated the requests using the chrome developer-tools: It seems that there are two simultaneous requests for the start page (
/lovelace/default_view
): One from the main browser thread and one from a service worker:The first one, coming from the main thread gets a
302 Found
redirect with aLocation
header redirecting to the/authorize
endpoint correctly using a new state parameter.However the second one yields a
303
Response and aLocation
header containing an old expiredstate
parameter, which finally results in an "invalid authorization response state and no default SSO URL is set, sending an error"400
error.As I cannot see an entry corresponding to the second request in the
access_log
, I guess the second one will be the result of some illegal caching? (There is not even a single303
redirect in theaccess log
.)The chrome
.har
file and some relevantaccess_log
anderror_log
lines are attached. (I guess I should invalidate my IDP session now..)Do you have any hints how to prevent this kind of caching? (As you can see there are already "no-cache" headers present.)
Cheers,
--leo
ha.kloburg.at-service-worker-state.har.zip
Beta Was this translation helpful? Give feedback.
All reactions