IDP v3 relying-party provider?

[Klingenstein, Nate]

Jeff,


The property is just a simple string that is ingested by a bean in the system directory.  Find the bean and then add a p:responderId reference to that bean in the relying party override bean.  Here are the analogies in system/.


system/conf/relying-party-system.xml:    <bean id="entityID" class="java.lang.String" c:_0="%{idp.entityID}" />
system/conf/relying-party-system.xml:        p:responderId="#{getObject('entityID')}"



Sorry for brevity, bicycle crash, two hands soon,

Nate.

________________________________
From: users <users-bounces at shibboleth.net> on behalf of Jeff McCullough <jeffmc at berkeley.edu>
Sent: Saturday, March 11, 2017 8:29:48 PM
To: Shib Users
Subject: IDP v3 relying-party provider?


Back in the V2 IDP relying-party configs there was provider attribute that was part of the overrides. I mistakenly put the incorrect entityId (used the server URL)  for the IDP for a couple of Service-Now configs. Though it was incorrect, it did work because the SN configs matched. In the V3 IDP that attribute is part of the idp.properties file. I’m guessing I’m going to need to go back and correct the SN configs, but there may be a possible override for the IDP provider. Is there?

Thanks,
Jeff

--
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/20170312/8e84bec7/attachment.html>