I missed a bug when you made the changes to update it to 2.0.
In shibresponder your getHeader is correct, but not in shibauthorizer. In shibauthorizer it is only looking for the new headers that will be sent as env vars to the application. You want to search in the headers of the current request.
Just copy the code from shibresponder or use the patch.
I'm starting to upgrade the 1.3 SPs that are using lighttpd so I'm only seing these bugs now...
That should hold until after the next release when I'll split the API to solve it.
Scott Cantor August 7, 2008 at 11:03 AM
Yeah, I'm still working through scenarios (that's why I'm not closing it yet, despite the "resolved" state), but that's the one I was double checking on here. You're correct that they're cleared first, but I probably will need to add code for that.
I agree, splitting that API is better, but it's not possible this late in a cycle.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
I missed a bug when you made the changes to update it to 2.0.
In shibresponder your getHeader is correct, but not in shibauthorizer. In shibauthorizer it is only looking for the new headers that will be sent as env vars to the application. You want to search in the headers of the current request.
Just copy the code from shibresponder or use the patch.
I'm starting to upgrade the 1.3 SPs that are using lighttpd so I'm only seing these bugs now...