Replies: 1 comment 1 reply
-
the server debug logs would show you what is happening i.e. if the header really is received etc. |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Hey folks,
I'm trying to setup FreshRSS which uses this module to enable OIDC, and I'm having some issues getting it work. Specifically, I believe this module is redirecting the browser to the OIDC server (Authelia, in my case) but specifying
http://freshrss.example.com/i/oidc
as theredirect_url
param, where it should be usinghttps
:https://freshrss.example.com responds
with 302 →https://freshrss.example.com/i/?rid=684f3434e5da9
https://freshrss.example.com/i/?rid=684f3434e5da9
responds with 302 →https://sso.example.com/api/oidc/authorization?response_type=code&scope=openid%20profile%20groups%20email&client_id=freshrss&state=Pi-WuYmW-p53E8wAihSo4-PSPEw&redirect_uri=http%3A%2F%2Ffreshrss.example.com%2Fi%2Foidc%2F&nonce=sVviq-R1t-X2rCglT5PHL2Y2x4o2pEFd3EhzWKh6SpI
Note the
redirect_uri
in the second response. I use Caddy as a reverse proxy, which is sending throughx-forwarded-proto=https
in the headers, so I'm a bit stumped as to why this is happening. Apache Configuration:The relevant environment variables are:
If anyone has any suggestions for what's going on here, that would be appreciated!
Associated FreshRSS bug: FreshRSS/FreshRSS#7658
Beta Was this translation helpful? Give feedback.
All reactions