Role-Based Authentication (RBA) in E2E Test Automation

Role-Based Authentication (RBA) in E2E Test Automation allows administrators to control access to different features of the platform by defining user roles. This ensures secure and appropriate access to specific screens, actions, and components within the application.

Key Features:

• Application Screen Permissions
• Role Actions Mapping
• Authentication Roles
• SSO Role Configuration

🔹 Application Screens

The Application Screens tab allows you to control the visibility and accessibility of different screens in E2E Test Automation based on user roles. In this section, you can define which actions a user role can perform on specific screens, as well as manage hidden components and access rights.

Key Components:

Screen Names:

Displays the list of all screens in E2E Test Automation.

Actions:

Defines what actions can be performed on each screen, including View, Create, Update, and Delete.

Hidden Component:

Allows you to hide certain components on the screen based on roles. This can be configured for each screen.

Manage Screen:

Click on the three dots next to a screen to manage the actions for that screen. In the Manage Screen page, you’ll find the following:

Possible Actions for this Screen:

Actions like View, Create, Update, and Delete are listed. You can choose which actions are allowed for different roles.

Action Role Mapping:

This section enables administrators to map actions to specific roles. For each role, you can define what actions (like View, Create, Update, Delete) are permitted.

🔹 Authentication Roles

In the Authentication Roles tab, you can view and manage the roles created for your company. These roles determine what access different users have to the E2E Test Automation system.

Managing Roles:

View Existing Roles:

Roles like Company Admin, Architect, Team Member, and Read Only Partner are displayed here.

Add New Role:

Click on the Add New Role button to create a new role. Fill out the role name, and E2E Test Automation will automatically generate a Role Code. Click Save to create the role.

🔹 SSO Configuration

Single Sign-On (SSO) configuration allows you to integrate E2E Test Automation with your company’s existing authentication system. By mapping your SSO roles to E2E Test Automation roles, you can manage access across both platforms seamlessly.

Steps to Configure SSO:

1. Go to the SSO Configuration tab.
2. Click on Add New to configure a new SSO mapping.
3. In the form, fill out the following:
   • Field Name (SSO): The unique name from your SSO system (e.g., ds_labs_sso).
   • SSO Role: The role in your SSO system (e.g., Admin, User).
   • E2E Test Automation Role: In the dropdown, select the corresponding E2E Test Automation role (e.g., Tech. Partner, Team Member).
4. After filling out the information, click Save to complete the configuration.

🔹 Key Aspects to Consider

Access Control:

RBA ensures that only authorized users have access to specific actions and screens within E2E Test Automation. This helps maintain a secure environment by enforcing the principle of least privilege.

Role Flexibility:

You can create as many roles as needed and map them to different screens and actions. For example, the Manager role may have access to more features than the Team Member role.

SSO Integration:

By integrating your SSO system, you ensure that users are automatically assigned the correct roles in E2E Test Automation based on their SSO credentials, providing a seamless experience for logging in and managing access.

Granular Control:

Administrators have granular control over what each user role can view, create, update, or delete, making it easier to tailor access to your team’s specific needs.

Summary

Role-Based Authentication (RBA) in E2E Test Automation provides a structured approach to manage user access. By defining roles and permissions, you can ensure secure and role-appropriate access to different screens and actions in the platform. This functionality is complemented by SSO configuration, allowing easy integration with external authentication systems.

With Role-Based Auth, you can:

• Control user access based on roles
• Set permissions for different screens and actions
• Integrate with your company’s existing SSO system

By setting up roles and managing permissions appropriately, you ensure that your E2E Test Automation environment remains secure and efficient.