Page tree
Skip to end of metadata
Go to start of metadata

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

OpenAthens SP or OpenAthens Cloud

For both OpenAthens SP and OpenAthens Cloud, the procedure is the essentially the same.

  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

OpenAthens Cloud will start to use this discovery service immediately.

OpenAthens SP, as with any configuration change, will need a webserver restart to pick up and start using the new settings.

If you are in any federations other than the OpenAthens federation they will have to update your metadata to include valid discovery return URLs before discovery will work - e.g:

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

For OpenAthens Cloud:
<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

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 add your discovery return endpoint to the metadata of every federation you are active in. 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 add your discovery return endpoint to the metadata of every federation you are active in. 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.

  • No labels