Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Wayfinder uses the SAML DS protocol and as long as your SP software does too it is 's just a case of configuring it to use Wayfinder as the discovery service. Some common SPs are covered below:

...

Code Block
languagexml
<idpdisc:DiscoveryResponse Binding="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol" Location="http://connect.openathens.net/saml/2/auth" index="1"/>

See also: Discovery

OpenAthens SP

  1. Sign in to the publisher dashboard (https://sp.openathens.net)

  2. Select the application in question and go to its configuration tab

  3. Scroll to the  discovery method section and select the radio button for the central discovery service

  4. If it doesn't already say so in the box, enter https://wayfinder.openathens.net  

  5. Save changes

...

Code Block
languagexml
<idpdisc:DiscoveryResponse Binding="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol" Location="https://yourdomain.com/oa/disco-ret" index="1"/>"

See also: Discovery

Shibboleth

You will need to do three things:

Add a discovery response binding to your metadata in the <Extensions> section- e.g:

...

<Extensions>
   ...
      <idpdisc:DiscoveryResponse xmlns:idpdisc="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol" Binding="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol" Location="https://shibsp.yourdomain.com/Shibboleth.sso/DS" index="1"/>
   ...
</Extensions>

... then add the discovery service to your shibboleth.xml configuration file in the SSO section in place of any singular IdP definition:

...

 <SSO
     discoveryProtocol="SAMLDS" discoveryURL="https://wayfinder.openathens.net">
     SAML2 SAML1
 </SSO>

Finally, you will need to ensure the discovery response endpoint you added to your own metadata is picked up by each federation you are active in. How this is done can vary by federation, but you will usually have to tell them.

If you are in the OpenAthens federation you will need to add the discovery return URL to your SAML endpoints via the SP dashboard:

  • Once you are logged in at sp.openathens.net, select your application
  • Go to the SAML endpoints tab and click the add endpoint button
  • Select discovery return URL, enter the value and click done
  • Click Save changes
  • It will take up to 15 minutes for the change to take effect

SimpleSAML.php

Set the options in authentication.php:

  • 'discoURL'  => 'https://wayfinder.openathens.net' 
  • 'idp' => null

Finally, you will need to ensure the discovery response endpoint you added to your own metadata is picked up by each federation you are active in. How this is done can vary by federation, but you will usually have to tell them.

If you are in the OpenAthens federation you will need to add the discovery return URL to your SAML endpoints via the SP dashboard:

  • Once you are logged in at sp.openathens.net, select your application
  • Go to the SAML endpoints tab and click the add endpoint button
  • Select discovery return URL, enter the value and click done
  • Click Save changes
  • It will take up to 15 minutes for the change to take effect

Other SP software

Add according to their instructions and then update the federation metadata as above.

Troubleshooting

No entities appear in Wayfinder

...

Include Page
_wayfinderShib
_wayfinderShib

SimpleSAML.php

Include Page
_wayfinderSimpleSAML
_wayfinderSimpleSAML

Other SP software

Add according to their instructions and then update the federation metadata as with Shib or SimpleSAML above.

Troubleshooting

No entities appear in Wayfinder

You may not be live in any federations yet. To check that, you would download that federation's metadata and check that your entity appears. If it's there check that it includes a <idpdisc:DiscoveryResponse> section that specifies Wayfinder. The REFEDs metadata explorer tool is also an option but may be a day behind (https://met.refeds.org/)

Unexpected entities appear in Wayfinder

Your entity appears in one of the federations that Wayfinder is aware of, or you have debug mode turned on.

  • Federations -
    • The federation toggles on your connection in the dashboard do not affect your appearance in other federations. They only affect which metadata is available to your application, not Wayfinder
    • EduGAIN means that as well as only needing to join one Academic federation to appear in many, there can be a delay between updates to the metadata in the federation you registered in and the other federations that include it picking up the change. Timezones and weekends play a part in how long it could take
  • Debug mode - this will, when enabled on your browser, tell Wayfinder to include entities that have a hide from wayf entity category on them.