Different behavior in X-FORWARED-USER after updating to 2.4.15.4 #1196
Closed
HolgerHees
started this conversation in
General
Replies: 3 comments 2 replies
-
I think you've spotted a serious bug... you probably have set |
Beta Was this translation helpful? Give feedback.
1 reply
-
2 times, yes. :-) I use "OIDCPassClaimsAs environment" and it fixed it for me ;-) |
Beta Was this translation helpful? Give feedback.
0 replies
-
thanks for this fast response and fix. Will close this discussion and look forward for 2.4.15.5 |
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
-
In version 2.4.15.3 I had the following apache configuration.
the result was that I had the following ENV variables
HTTP_X_FORWARDED_USERFULLNAME => value of mapped userfullname
HTTP_X_FORWARDED_USERGROUP => value of mapped usergroups
HTTP_X_FORWARDED_USER => value of mapped username
REMOTE_USERFULLNAME => value of mapped userfullname
REMOTE_USERGROUP => value of mapped usergroups
REMOTE_USERNAME => value of mapped username
after upgrading from version 2.4.15.3 to 2.4.15.4 (same apache container, just compiled the new openidc version inside)
HTTP_X_FORWARDED_USERFULLNAME => value of mapped userfullname
HTTP_X_FORWARDED_USERGROUP => value of mapped usergroups
HTTP_X_FORWARDED_USER => value of OIDC_CLAIM_email
REMOTE_USERFULLNAME => value of mapped userfullname
REMOTE_USERGROUP => value of mapped usergroups
REMOTE_USERNAME => value of OIDC_CLAIM_email
this time, I have no idea which commit could be related to it.
I just reverted back to version 2.4.15.3 and everything works like before again.
Beta Was this translation helpful? Give feedback.
All reactions