Catalyst Authentication features can be used in the following scenarios:
An internal web forum, meant for the employees of an organization to discuss and gather information about the activities and tasks undertaken in various departments, uses Catalyst Authentication to manage its users. The collaborators of the web app development team can invite users to access the forum, assign and create custom roles for users, modify user information, or delete users from the console.
The application provides three levels of access to its various users: App Administrator, App Moderator, App User. The users of the app user role can only submit posts in the forum, while the app moderators can approve or decline the content submitted for approval, and the app administrators can also permanently delete the content in the forum. These permissions for the user roles are configured in the Data Store and File Store.
An application that can be accessed by different kinds of users, and based on the type of user you can have three different types of login element. For example, if your application is accessed by members of your organization, you can choose to design the login page from the console to ensure only to contain social login elements, instead of a generic login form. For the same application you can also configure and design a dedicated login page with a conventional login form for new end-users that happen to be outside your organization.
A travel planner web app requires its widget to be embedded in a hotel booking website, developed by one of its auxiliary companies. The hotel booking application also requires access to the travel web app’s function endpoints, to obtain specific data of their common customers. The travel web app makes use of Catalyst Authentication to quickly authorize the domain of the auxiliary company, and CORS and iFrame for it. The travel planner web app also implements a Google sign-in option in its client application, and manages it from the Catalyst console.
Catalyst Authentication offers you the option to enable or disable public signups. If you are building an application where you do not want to provide a login element at all and yet authorize users to your application, you can do so by disabling public signups and directly adding the end-user from the console. If you wish to enhance the security of your application further, you can enable the Custom User Validation and create a Catalyst Basic I/O functions to validate the user details and add them to your application.
Every company has an identity and branding colors and font that they follow to stand out and become recognizable. Using Catalyst Authentication, you can maintain brand consistency when it comes to sending out sign up emails and password action emails without any additional coding. The console offers you email templates tthat you can use to style your user authorization emails in a manner that resonates with your brand.
Last Updated 2023-05-08 18:05:05 +0530 +0530
Send your feedback to us