In order for your institution to integrate with Unibuddy to facilitate Single Sign On, you must be integrated with an Identity Provider which is compatible with either OIDC or SAML authentication frameworks. These are standard frameworks that we work with.
For SAML (e.g Azure AD):
Unibuddy will provide 2 pieces of information:
Callback URL (ACS) - known as REPLY URL in Azure https://auth.unibuddy.co/samlv2/acs
Issuer ID - known as Identity or Entity ID in Azure and is unique to you.
You can adds these values to your IdP
These are the only 2 required pieces of information in Azure and they are both supplied to section 1 of the Azure SAML SSO setup
Once these are setup, let Unibuddy know the certificate in Base64 format ( Section 3 in Azure) and Login URL (Section 4 in Azure)
Unibuddy will then complete the SSO setup
For OIDC:
Create a client application representing Unibuddy in the Identity Provider's system and take note of the Client ID & Client Secret
Share the following items with Unibuddy team:
Client ID
Client Secret
Authorization endpoint
Token endpoint
User information endpoint
At this point, Unibuddy will share a redirect URL with your university, pass this URL to your IT team and ask them to add it to the client application. It will look something like this
https://auth.unibuddy.co/oauth2/callbackAsk your IT team for confirmation that the redirect URL has been saved, and let Unibuddy know.
Unibuddy will let you know when the configuration is complete, and then your integration is complete.
Unibuddy will also setup and share a university-specific vanity URL that your teams will need to use to set the necessary SSO cookies on browsers.
The Unibuddy team will work with you to test out the integration.