Support for X509SubjectName Name ID

[Ullfig, Roberto Alfredo]

So I was working on two of these non-InCommon ones yesterday and both had the same issue - so it seems like there's a new pattern to see for some of the new service providers. One was Azure and the other I'm not sure. Anyway, usually in the past I have this in relying-party for the non-InCommon ones:

                    p:signResponses="false"
                    p:signAssertions="false"
                    p:encryptNameIDs="false"
                    p:encryptAssertions="false"

but in this case they both expected signed responses. Have never seen that before but maybe it's an Azure thing.

---
Roberto Ullfig - rullfig at uic.edu
Systems Administrator
Enterprise Architecture and Development | ACCC
University of Illinois - Chicago
________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Thursday, May 14, 2020 10:27 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Support for X509SubjectName Name ID

On 5/14/20, 11:23 AM, "users on behalf of Ullfig, Roberto Alfredo" <users-bounces at shibboleth.net on behalf of rullfig at uic.edu> wrote:

>        <bean parent="RelyingPartyByName" c:relyingPartyIds="https://immuware-uic.azurewebsites.net">
> 🙂

"Duh"

No, never run into it.

-- Scott


--
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200515/4945e280/attachment.htm>