Role-based Authentication

1) Role-based authentication is a template authentication mode, in which the administrator configures templates of different access permissions based on the user’s department, role, etc. For example, users with the permission of front-line technical support are allowed to view Template B only and will be prompted that they have no permission if they try to access Template A.

2) Role-based authentication is suitable for large systems with a number of users and a few departmental- and role-based templates.

3) In Role-based authentication, users are required to successfully log into the system first to have their permissions determined before viewing the template. Successful login means a user logs into the Report system, verifying his/her user name and password configured in the system. It is generally used in conjunction with User Authentication. In other words, the authentication of user names and passwords depends on the settings of User Management>Global Settings .

1. Enable the authentication and select a template

When enabled, all templates need authentication by default. Please refer to Template Authentication - II. Introduction to Template Authentication - 3. Enable the authentication and select a template.

2. Select Role-based Authentication

1) Enable Role-based Authentication by selecting [Management System]>[Template Authentication]>[Global Settings].

2) Save and display the Permission Assignment page, showing all the departments, roles and users set in the User Management.

3) Set Permissions

• Permissions can be assigned separately to departments, roles or users.

• After selecting a department or a role or a user for permission setup, you can assign View and Data Entry for the list of templates to be authenticated on the right. View and Data Entry refer to the functions of General Preview and Data Entry Preview.

• By default, all templates are locked and require permission. Templates with an open lock can be accessed after authentication. Click on theLock icon to set up the templates.

Example: Select the user Jack, allowing it to view the template GettingStartedEN.cpt and preventing it from Data Entry.

3. Preview

Take GettingStartedEN.cpt as an example.

1) Perform Pagination Preview on GettingStartedEN.cpt: http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt, and type in user name Jack to log in and view.

2) Perform Data Entry Preview on GettingStartedEN.cpt: http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt&op=write, and type in user name Jack to log in. There is no permission to view Data Entry.

3) Perform Pagination Preview on GettingStartedEN.cpt: http://localhost:8075/webroot/decision/view/report?viewlet=GettingStartedEN.cpt, and type in user name Lily to log in. There is no permission to view reports.