<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>:%s/Find the bean/Make a similar bean in a location of your
      choosing outside the system directory<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 03/12/2017 04:40 AM, Klingenstein,
      Nate wrote:<br>
    </div>
    <blockquote
cite="mid:CY4PR01MB2214B3E2A1D6CF409F2211CDDE220@CY4PR01MB2214.prod.exchangelabs.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Exchange Server">
      <!-- converted from text -->
      <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
      <meta content="text/html; charset=UTF-8">
      <style type="text/css" style="">
<!--
p
        {margin-top:0;
        margin-bottom:0}
-->
</style>
      <div dir="ltr">
        <div id="x_divtagdefaultwrapper" dir="ltr"
          style="font-size:12pt; color:#000000;
          font-family:Calibri,Arial,Helvetica,sans-serif">
          <p>Jeff,</p>
          <p><br>
          </p>
          <p>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/.</p>
          <p><br>
          </p>
          <div>system/conf/relying-party-system.xml:    <bean
            id="entityID" class="java.lang.String"
            c:_0="%{idp.entityID}" /><br>
            system/conf/relying-party-system.xml:       
            p:responderId="#{getObject('entityID')}"<br>
          </div>
          <br>
          <p><br>
          </p>
          <p>Sorry for brevity, bicycle crash, two hands soon,</p>
          <p>Nate.<br>
          </p>
        </div>
        <hr tabindex="-1" style="display:inline-block; width:98%">
        <div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
            color="#000000" face="Calibri, sans-serif"><b>From:</b>
            users <a class="moz-txt-link-rfc2396E" href="mailto:users-bounces@shibboleth.net"><users-bounces@shibboleth.net></a> on behalf of Jeff
            McCullough <a class="moz-txt-link-rfc2396E" href="mailto:jeffmc@berkeley.edu"><jeffmc@berkeley.edu></a><br>
            <b>Sent:</b> Saturday, March 11, 2017 8:29:48 PM<br>
            <b>To:</b> Shib Users<br>
            <b>Subject:</b> IDP v3 relying-party provider?</font>
          <div> </div>
        </div>
      </div>
      <font size="2"><span style="font-size:10pt;">
          <div class="PlainText"><br>
            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?
            <br>
            <br>
            Thanks,<br>
            Jeff<br>
            <br>
            -- <br>
            To unsubscribe from this list send an email to
            <a class="moz-txt-link-abbreviated" href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a></div>
        </span></font>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    <br>
  </body>
</html>