If your authentication identity provider (IDP) is in a federation that Talis is also a member of, then all we would need is the entity id of your IDP.
If your IDP is not in any federation then we will need your signed federation metadata in order to add your IDP to our configuration. For Microsoft Entra (formerly Azure) the URL looks something like this.
https://login.microsoftonline.com/<uniidentifier>/federationmetadata/2007-06/federationmetadata.xml?appid=<appid>
- The <uniidentifier> is a long code unique to your azure instance.
- The <appid> is an identifier for the specific app that you will have to configure in Azure. You will need to trust our SAML Service Provider (SP). Our entity ID is also the URL that you can get our SP metadata from.
EU/APAC - https://login.talisaspire.com/entity
Canada North America - https://login.ca.talis.com/entity
You will also need to be sure to release to us, as a minimum, the attributes in the metadata which are marked as required. However, you will probably also want to consider additional attributes. These may vary between Talis Applications. Your Talis consultant will advise you which additional attributes need to be considered.
These articles contain information about attributes for specific products or purposes:
- Automatic Profile Creation in Talis Aspire Reading Lists - For Talis Aspire
- Automatic Profile in Talis Elevate - For Talis Elevate
- Devolved Authentication - For Talis Aspire
- Implementing Devolved Constraints or Entitlements - For Talis Aspire