Heather Peake wrote:
> I've tested my IDP against the UK Federation thing https://.../printenv
and
> I get the same result whether I include the jdbc connector bit or not
which
> is why I think I'm mangling the attributes rather than releasing them!
Looking at that SP, it isn't seeing any attributes being released:
2008-05-15 15:43:06 INFO Shibboleth-TRANSACTION : Caching the following
attributes after AAP applied for session (ID:
_ce95494d0d69c26e56010050fde39749) on (applicationId: default) for principal
from (IdP: https://shibidp.wnc.ac.uk/shibboleth) {
2008-05-15 15:43:06 INFO Shibboleth-TRANSACTION : }
There's nothing in its other log to indicate that attributes were being
received
but filtered out at the SP end, so it looks like they are not being sent,
so I think you're on the right track looking at your arp/DB. You can
tell what attributes you are releasing from your end by turning up
IdP logging to DEBUG and looking at the attribute response message it sends
(you may also find that level of logging helpful to find out why it is
not sending the attributes you want).
Fiona.
|