locked
SubjectConfirmationData is missing recipient

    General discussion

  • Hi,

    I'm writing a .NET client and when I request a SAML token using the 'RequestSecurityToken' and applying to a EndpointAddress realm (that is configured in ADFS in the RelyingPartyTrust area), I get back a SecurityToken but it is missing the Recipient value (SubjectConfirmationData). 

    I've check the entry in the RelyingPartyTrust and it does contain an EndPoint Recipient address.

    Does anyone know how to get that value?
    Friday, October 12, 2012 4:27 AM

All replies

  • Hi,

    I'm writing a .NET client and when I request a SAML token using the 'RequestSecurityToken' and applying to a EndpointAddress realm (that is configured in ADFS in the RelyingPartyTrust area), I get back a SecurityToken but it is missing the Recipient value (SubjectConfirmationData). 

    I've check the entry in the RelyingPartyTrust and it does contain an EndPoint Recipient address.

    Does anyone know how to get that value?

    I have the same issue ! Some help with this issue?

    gaurav

    Wednesday, November 21, 2012 3:05 PM
  • Hi,

    I am also receiving this same issue and was wondering if anyone has solved how to get the recipient value added to the SubjectConfirmationData.

    Thanks in advance!

    Justin

    Thursday, February 13, 2014 2:26 AM
  • Same issue. Trying to resolve it with MS support now.
    Thursday, June 26, 2014 9:01 PM
  • Same issue here :(

    Augusto Ruiz :: http://geeks.ms/blogs/aruiz

    Tuesday, July 15, 2014 8:02 AM
  • Hi!

    I've found a workaround. See this question.

    Cheers!


    Augusto Ruiz :: http://geeks.ms/blogs/aruiz

    Wednesday, July 16, 2014 9:27 AM