Closed rabb1t closed 9 years ago
I use proxy_pass
-based backends (listening for headers) so I've not tested a fastcgi_pass
backend before with params before. At an educated guess, I would try adjusting the line:
fastcgi_param REMOTE_USER $http_remote_user if_not_empty;
to
fastcgi_param REMOTE_USER $upstream_http_variable_remote_user if_not_empty;
as the Shibboleth authorizer should be returning Variable-REMOTE_USER
headers & populating this variable.
There may be some sort of race condition whereby the original $http_remote_user
variable isn't (always) populated/overwritten when the variables get copied out of the upstream Shibboleth authorizer request. It's been a while since I wrote the code, but I recall seeing something mentioned about issues like this might arise when manipulating headers inside Nginx, which is what the nginx-shib module is doing.
@rabb1t did this solve the issue?
Hello,
The problem is still persist unfortunately. But it is not related to nginx-http-shibboleth
module at all.
It seems that the problem is in our frontend part. When the user logs out (from the web site in our case), the frontend doesn't call the shibboleth module to start the 'Logout' procedure and the session cache are still exist.
Hello, David!
First of all thank you for the work you've done on this module and for all great articles you've written! I've found very strange problem and hope you can point me in the right direction.
Sometimes when I'm trying to login via shibboleth the variable
'REMOTE_USER'
is set correctly but sometimes it's not. Nginx's log files indicates that shibboleth daemon provides proper variable'Variable-REMOTE_USER'
and the shibboleth module copies it correctly on every single requestshib request authorizer copied header: "REMOTE_USER: john.doe@local.lan"
But periodically it seems that somehow this header isn't transmitted properly further to Nginx. Any help on this problem will be appreciated!
Here are the cut of nginx error.log files:
Here are the cut of my nginx configuration: