Rewriting shib headers as proxy request headers: Session ID?

Christopher Piggott cepasp at rit.edu
Tue Feb 20 23:27:52 UTC 2024


> It's set at the same time, they all get set in the same step. If you want to 
> be absolutely pedantic testing it, it sets Shib-Application-ID in the 
> immediately preceding line of code, so it's not possible for one to be set 
> and not the other.

Curiously, I don't get that one, either.  In fact, all the ones that start 
Shib_ that I have tried so far don't come through.

These work:

                RequestHeader set Remote-User %{SHIB_mail}e env=SHIB_mail
                RequestHeader set X-Given-Name %{SHIB_givenName}e 
env=SHIB_givenName
                RequestHeader set X-Last-Name %{SHIB_sn}e env=SHIB_sn

These do not:

                RequestHeader set X-Shib-Handler %{SHIB_Shib_Handler}e 
env=SHIB_Shib_Handler
                RequestHeader set Shib-Session %{SHIB_Shib_Session_ID}e 
env=SHIB_Shib_Session_ID
                RequestHeader set Shib-Session %{SHIB_Shib_Application_ID}e 
env=SHIB_Shib_ Application _ID


Yet with my env.py test cgi, they're all in the environment variables - same 
vhost, all asking for

	SHIB_Shib_Handler: https://odoo.gis.rit.edu/Shibboleth.sso
	SHIB_Shib_Application_ID: default
	SHIB_Shib_Session_ID: _ec51ecbe1446289507000c971c67ccb9
	SHIB_givenName: Christopher
	SHIB_mail: cepasp at rit.edu
	SHIB_sn: Piggott


Is there something special about the Shib_  environment variables?  They 
aren't really 'attributes' I suppose.

(Sorry it's confusing I added the attribute prefix SHIB_ ... it looks weird 
that it says SHIB_Shib_* on those, but it makes sense for regular attributes).





-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7132 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20240220/d6b3c986/attachment.p7s>


More information about the users mailing list