Sent Attributes

[Cameron Kerr]

Turn on the protocol debugging and you’ll get the entire SAMLResponse and and SAMLRequest, which is the most helpful thing to see in my experience.

The issue may well be that the attributes are not being mapped at the other end. Providing the protocol message gives the most clarity as to what needs to be mapped.

Knowing the SP implementation really helps.

Sent from my iPhone

On 30/05/2018, at 4:06 AM, Steven Teixeira <steixeira at csustan.edu<mailto:steixeira at csustan.edu>> wrote:

Assuming there’s nothing you don’t want to send via plaintext to them, a copy of the exact SAML response usually works for me.

Steven Teixeira

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Robert Lamothe
Sent: Tuesday, May 29, 2018 08:59
To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Sent Attributes

Hello,

    I'm working with an SP that's authenticating against my test IDP.  We've swapped metadata and that seems to work, I can connect to their SP, it redirects to my IDP, I authenticate and get a page that identifies the attributes that are being sent and yet the SP claims there are no attributes being delivered.


   I've tested against shibtest.org<http://shibtest.org> and everything looks good there, I've also had other SPs work against this IDP.


    I'm now in a "Your IDP isn't sending attributes" vs "Yes it is, the 'Information Being Provided to Service' page shows what's being sent" discussion.  How to I prove it beyond that?


Thanks
-Bob

--
Bob Lamothe
robert_lamothe at yahoo.com<mailto:robert_lamothe at yahoo.com>
KB1BOB
603-918-6336
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180529/ed20a4e8/attachment.html>