How can I get the Saml2SecurityToken.Assertion.Subject.NameId in the Subject form the testshib.org test server?

Peter Schober peter.schober at univie.ac.at
Wed Oct 15 08:16:11 EDT 2014


* W O <39a0d912abc at gmail.com> [2014-10-15 13:57]:
> Thank you for your answer. For rd.dev I get:
>  </ds:Signature>
>    <saml2:Subject>
>       <saml2:SubjectConfirmation
> Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
>          <saml2:SubjectConfirmationData Address="46.243.26.58"
> InResponseTo="_0b651836-f552-430c-90e4-e84e55d4eaa7"
> NotOnOrAfter="2014-10-15T11:54:38.962Z" Recipient="
> https://rp.dev/Auth/AssertionConsumerService"/>
>       </saml2:SubjectConfirmation>
>    </saml2:Subject>
> 
> I expect:
> 
>  <saml:Subject>
> *      <saml:NameID
> Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">MyId</saml:NameID>*

Testshib only announces support for transient NameIDs, as you can see
in the Testshib IDP's metadata.  If you're requesting something else
in your SAML2.0 authentication request (my reading of your "I expect"
above) that would explain the absence of the NameID in your case, but
its presence in other cases (like in my test with the Testshib SP).

So stop requesting a NameID format the IDP does not state it supports,
I would expect that to make a difference.
-peter


More information about the users mailing list