Closed GoogleCodeExporter closed 9 years ago
This is probably caused by you looking for the Shibboleth properties using
request.getHeader() instead of request.getAttribute(). Shibboleth attributes
are passed by mod_shib and mod_jk via attributes in the request object.
I'm also curious about why you decided to change the attribute names. In our
installation, mod_shib sends the capitalized names that correspond to the
traditional, CGI-inspired convention. I'm attaching a copy of our mod_jk
configuration for your reference. In there we specify the environment variable
names that will be sent by mod_jk to the Login servlet in tomcat/jboss.
Original comment by past...@gmail.com
on 19 Aug 2010 at 9:37
Attachments:
Thank you for the tip.
Looking at the jk.conf file that you provided I can see that 'JkEnvVar'
parameters in my current Apache configuration are missing. That is probably the
reason why I was receiving null values for all the attributes. As I said, this
is first time we are deploying Shibboleth SP, mod_shib and mod_jk (we are using
SAML protocol in our AAI federation, but without Shibboleth) so I had no
previous experience on how to configure things properly.
I'm currently on vacation and have a very limited access to our testing
environment, but as soon as I get back to work I'll try to fix things according
to your instructions.
Dubravko
Original comment by dubravko...@srce.hr
on 22 Aug 2010 at 6:38
Hi, I'm Faidon Liambotis, I work at GRNET's NOC and was the one that deployed
GSS on GRNET. A couple of comments from me:
* About using request headers to pass on attributes: this is a practice used in
the 1.3 days but is discouraged nowadays. Have a look at
https://spaces.internet2.edu/display/SHIB2/NativeSPAttributeAccess
and the spoof checking section. Also have a look at the "ShibUseHeaders" and
"ShibUseEnvironment" config options at:
https://spaces.internet2.edu/display/SHIB2/NativeSPApacheConfig
* About the attribute names, you can choose your own names at the
attribute-map.xml configuration file. If these are passed via the environment
to the application, you'll see the HTTP_* (capitalized & underscored)
convention used.
Original comment by parav...@gmail.com
on 27 Aug 2010 at 12:02
Since it's been a month with no feedback I'm assuming this is now resolved and
I'm closing the issue. If that is not the case, let us know.
Original comment by past...@gmail.com
on 28 Sep 2010 at 12:14
Original issue reported on code.google.com by
dubravko...@srce.hr
on 18 Aug 2010 at 3:02