Child pages
  • Tuakiri Federation Service SAML1 Support

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Introduction

Tuakiri requires that all services use SAML2.

When registering an IdP or an SP into Tuakiri, the Federation Registry only registers SAML2 endpoints and SAML2 NameID format.

This page provides the technical information for manually registering a SAML1 end-point. Note however, that for a SAML1 login to succeed, both the IdP and SP registration must have the SAML1 NameID and endpoints configured. Tuakiri does not provide any support this configuration, this page only provides the necessary technical background on manually adding the SAML1 endpoints for historical reference.

Service Providers

To support SAML1, compatible endpoints should be manually added during registration on the Tuakiri or Tuakiri-TEST federations. These endpoints can be manually added after initial registration to retroactively add SAML1 support.

Open the SP description and

Note

Remember to replace sp.example.org with the actual hostname of your Service Provider

Note

These exact URL of the services is implementation specific - the examples here are for the default values in Shibboleth SP 2.x

Identity Providers

In the IdP description:

Note

Remember to replace idp.example.org with the actual hostname of your Identity Provider

Note

These exact URL of the services is implementation specific - the examples here are for the default values in Shibboleth IdP 2.x