Replies: 1 comment
-
This issue is solved: in our case, we don't need to use OIDCRedirectURLsAllowed. Instead, we need to use OIDCXForwardedHeaders as described here: https://github.com/OpenIDC/mod_auth_openidc/wiki#8-how-do-i-run-mod_auth_openidc-behind-a-reverse-proxy. We are grateful for this excellent mod_auth_openidc to the authors! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We try to allow third-party access via OIDCRedirectURLsAllowed. The host of the target_link_uri is something like https://app.somehost.hu . OIDCRedirectURLsAllowed is defined as:
OIDCRedirectURLsAllowed ^https://app\.somehost\.hu ^http://localhost:8080 ^http://localhost
The application (incl. mod_auth_openidc) is running in a docker container so we use ProxyPass from the outer Apache2 server.
What do we miss?
Thanks, Péter Hanák
Beta Was this translation helpful? Give feedback.
All reactions