SAML Configuration Guide

1. Client registers Housing.Cloud as a new Service Provider in their respective Identity Provider (IdP) using the Endpoints below and creates the necessary Attribute mappings
2. Client shares the Metadata XML file with Housing.Cloud and confirms the Attribute names to be included in the Assertion
   1. e.g. fullName vs http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
3. Housing.Cloud registers the Identity Provider using the Client's Metadata file
4. Client should ensure that the appropriate audience(s) are provisioned to the Housing.Cloud Enterprise Application in their respective IdP
   1. For sandbox, this audience is primarily only the Housing/Residents Life Professionals and IT Professionals
   2. For production, this audience is typically all current students, Housing/Residents Life Professionals, and IT Professionals

Required Assertion Attributes

• NameID
  • Required NameID formats (or):
    • urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
    • urn:oasis:names:tc:SAML:2.0:nameid-format:persistent
• Email:
  • Supported attribute names:
    • http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
    • http://schemas.xmlsoap.org/claims/EmailAddress
    • mail
    • email 
• Name (full name):
  • Supported attribute names:
    • http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

Endpoints

• Sandbox:
  • SSO/ACS: https://udpdwbajlucpsnfrttva.supabase.co/auth/v1/sso/saml/acs
  • Default Relay State: https://udpdwbajlucpsnfrttva.supabase.co
  • Metadata/Audience URI/EntityID: https://udpdwbajlucpsnfrttva.supabase.co/auth/v1/sso/saml/metadata
• Production:
  • SSO/ACS: https://auth.housing.cloud/auth/v1/sso/saml/acs
  • Default Relay State: https://auth.housing.cloud
  • Metadata/Audience URI/EntityID: https://auth.housing.cloud/auth/v1/sso/saml/metadata

Unique Identifiers

Housing.Cloud supports two unique identifiers for SAML authentication and the institution must specify which they would like to leverage:

• email
• sisId