This article summarises the different user authentication options available to your subscribers
Read this article to understand how to:
- Enable subscribers to seamlessly access your Content Catalyst subscriber portal
- Ensure site security with a robust user authentication system
The user login experience varies depending on whether your site is using the Content Catalyst built-in authentication, OAuth authentication, or our proprietary publisher SSO framework.
Built-in authentication
If hosting a closed site, the user is immediately prompted to log in using either their username or email. If hosting an open site, once the user clicks the login link they get the login prompt.
- The registration link only appears if you have any accounts that allow registration
- The login form sub-heading is optional
- The login form terms and conditions paragraph is optional
🔔 The other non-optional text on the login form is all customisable - please contact the helpdesk if you wish to change this or the above optional settings.
OAuth-based Enterprise SSO with Okta or Azure AD
If you have OAuth-based SSO enabled for any account on your site, the login experience for all users changes slightly. The authentication flow starts with a prompt for the user's email address so the Publish Interactive site can determine whether to present the built-in login page as above or to hand this user's authentication flow over to Okta or Azure AD.
🚨 To ensure a smooth roll-out with your customer, it is important that users know to log in only with their registered email address and not their username.
Similar to the built-in login page above, there are optional and configurable text elements. Contact the Publish Interactive helpdesk if you want to change anything from the default.
Proprietary Publisher SSO
This method of user authentication bypasses the built-in authentication UI entirely. You will supply a login redirect URL to an authentication page which will replace our login prompts.