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
If you have your application server (Apache+openidc) behind a reverse proxy, which terminates the https session and the communication to the application server is done by http, you get a problem.
You get an error like this ... oidc_authenticate_user: the URL scheme (https) of the configured OIDCRedirectURI does not match
the URL scheme of the URL being accessed (http): the "state" and "session" cookies will not be shared between the two!
... while configuring openidc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If you have your application server (Apache+openidc) behind a reverse proxy, which terminates the https session and the communication to the application server is done by http, you get a problem.
You get an error like this ...
oidc_authenticate_user: the URL scheme (https) of the configured OIDCRedirectURI does not match
the URL scheme of the URL being accessed (http): the "state" and "session" cookies will not be shared between the two!
... while configuring openidc.
The problem is, openidc needs to consider the HTTP_FRONT_END_HTTPS variable around the code sequence ...
https://github.com/OpenIDC/mod_auth_openidc/blob/master/src/handle/request.c#L60
Maybe a simple switch to disable the scheme check, will also help to use openid in such environments.
Beta Was this translation helpful? Give feedback.
All reactions