If you are a member of the JISC Access Federation, you can pull Handshake's metadata from there.

If you are not a member of the JISC Access Federation, you can download a copy here.

Handshake's entityID is: https://app.joinhandshake.co.uk/sp
Handshake's AssertionConsumerService Post URL is: https://app.joinhandshake.co.uk/saml_consume

Attribute or NameID Suggestions

RequestedAttribute: FriendlyName="eduPersonPrincipalName"
Requested Format: NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"

NOTE: The attribute or NameID you specify should return a value matching the format of the auth_identifier field from your student syncs. You should specify the value you selected (either a NameID OR an attribute) in your Handshake SSO Preferences (after step 4 here). You should not use both NameID and an attribute.

ADFS or Azure AD Configuration

We've created a guide to configure your claim rules if you are using ADFS as your Identity Provider, which can be found here. The claim rule configuration for ADFS and Azure AD will be almost identical, so you can use the above guide as a reference if you are using Azure. The main difference between these two Identity Providers is the following setting under your Handshake SSO Preferences page:

You will need to leave this box unchecked (disabled) if you are using ADFS or Azure AD.

If you are configuring an Azure AD SAML integration, in Azure you will only need to enter the Entity ID and Reply URL shown above. Copy the App Federation Metadata URL and import it into the "Import" field of your SSO Preferences page in Handshake. You can leave the NameID Format blank for the purposes of testing(or if you know the format of the attribute you will be assigning as the "auth_identifier" for students, use that), and ensure "Requested authentication context?" is un-checked before testing! 

Setting SSO up on Handshake is self-service! After your career services admin has added you to Handshake you can begin SSO Setup and Testing.

Contact our Support Team.