Getting RemoteUserInternal working with a custom header
Youssef Ghorbal
youssef.ghorbal at pasteur.fr
Tue Nov 10 11:28:05 EST 2015
>> tcpdump shows that the header is provided to tomcat (in the HTTP request) and correcly formatted (I double checked this)
>
> Tomcat alone, or Apache? You could try the snoopservlet or similar dumping sample and see if you can verify what Tomcat is seeing outside the IdP.
Tomcat is behind a F5 Reverse Proxy (no Apache involved)
The tcpdump was done on the tomcat side.
I’ve just checked with a snoopservlet, Tomcat do see the custom header.
>> I tried, for testing puposes, replacing the X-Username in authn/remoteuser-internal-authn-config.xml with a header that I’m sure always exists (I tried with the Host header for example) and with that header everything worked fine :
>
> That sort of implicates your header / infrastructure I would say.
>
>> So either :
>> - checkHeaders is empty when called (IdP is not honoring the authn/remoteuser-internal-authn-config.xml, or the list is emptied earlier in the IdP code)
>
> If that were true, your sanity check wouldn't have worked.
So what's left is that request.getHeader returns null (ie the HttpServletRequest gets altered earlier in the code) does this seems likely ?
Thank you for your help.
Youssef
More information about the users
mailing list