Skip to main content

Introduction

Last updated 26/02/2024

What is SSO?​

A user can access numerous applications with just one set of login credentials (such as their name and password) thanks to Single Sign-On, a user authentication service. In essence it makes logging in easier by doing away with the requirement for unique usernames and passwords for every application.

You can setup single sign-on (SSO) for your users to access your applications from anywhere and provide a quick and easy sign-on experience to keep your users productive and reduce time managing passwords. Setting up SSO will help ensure that only authorized users have access to your applications and data.

Please refer to the Introduction chapter for Authentications to understand who can manage authentication records and to have an overview of the fields on the Authentications form.

Supported Authentication Types​

Please refer to the following sites for information on the different authentication types.
OUATH 2.0
OpenID
SAML

info
To have this feature available in your application, a paid subscription is required. Visit our pricing site for more details.

Setting Up SSO Authentication With Your Provider​

When setting up your SSO authentication with your provider, you will need to register the Redirect URI with them, this will be the hostname you have deployed followed by the redirection URL of 'sso_login' for OAuth2.0 or OpenID, and saml/acs for SAML 2 authentications.

For example, if your application is called myapp, and the instance name is called default, the redirect URI will be formatted as follows:

 Under user 'dev' in the Development environment:
https://dev-default-myapp-nameprefix.5au.dev/sso_login
https://dev-default-myapp-nameprefix.5au.dev/saml/acs

Under user 'admin' in the Development environment:
https://admin-default-myapp-nameprefix.5au.dev/sso_login
https://admin-default-myapp-nameprefix.5au.dev/saml/acs

If testing in the Testing environment, it will always be the testing calculated hostname:
https://default-myapp-nameprefix.5au.dev/sso_login
https://default-myapp-nameprefix.5au.dev/saml/acs

If deployed in the Production environment, it can also be the production name you have allocated, for example:
https://business.com.au/sso_login
https://business.com.au/saml/acs