Overview
Application Scenarios
When a user accesses the system, the system needs to know what permissions the user has and what the user can see. FineBI can fulfill this task.
Integrating FineBI templates into user’s system means using the full path of the template preview as the link address of user system nodes. Therefore, viewing the templates in user system is equivalent to directly previewing the templates, so template permission control can also be considered as permission control for directly previewing the templates
Functions
If you need to integrate FineBI into your existing systems and view FineBI dashboards when logging in the system, you need authentication with a username and password by default.
Besides, FineBI provides Role Permission Authentication and Digital Signature Authentication to control which template a user can view. You can select AUTH Method according to your needs.
| Method | Introduction |
|---|---|
Authentication User Password Only | You need to log in to authenticate. After logging in, all users' permissions are the same and you can see all the templates. |
| Role Permission Authentication | You need to log in to authenticate. After logging in, according to the role, users have different permissions, and every user can only view the templates that they have permissions for. |
| Digital Signature Authentication | You need to log in to authenticate. You can authenticate the request for templates through digital signature. Only when the signature information is proved legal by FineBI Digital Signature Authentication, can you view the templates. |
Note:
1. Integrating FineBI templates into user system means using the full path of the template preview as the link address of the user system node. Therefore, viewing the templates in user system is equivalent to previewing the templates directly, so template permission control can also be considered as permission control for directly previewing the templates.
2. Template Permission needs to be integrated with user system.
Notes
1. When you disable Template Permission and enable it again, the previous settings will remain the same.
2. Template Permission needs to be integrated with user system. For more details, refer to the table below:
| Template Permission Feature | Decision Platform Feature | Effect |
|---|---|---|
| Not purchase | / | Unable to use the Template Authentication. |
| Purchase | Not purchase | You can use Template Authentication, and it will apply to the templates that you set. You cannot mount the templates on the platform and can only access through a link such as http://localhost:37799/webroot/decision/v5/design/report/3a830560f7084d72bbd029155a92c556/view. |
| Purchase | You can use Template Authentication. 1. Template Authentication is effective for the templates that are accessed through a link like http://localhost:37799/webroot/decision/v5/design/report/3a830560f7084d72bbd029155a92c556/view. 2. Template Authentication is not effective for the directory templates that are accessed through platform. 3. Template Authentication is effective for the homepage templates that are accessed through platform. |
Template Authentication
Logging in Decision-Making Platform
Admin logs into FineBI Decision-Making Platform and click Manage > Template Authentication.
Or enter http://IP:port/webroot/decision#management/template-authority in the browser address bar.
Template Authentication is disabled by default, which means anyone can view all the current templates.
Enabling Template Authentication
Click Permission Configuration in the upper left corner to enable Template Authentication and configure the templates that you need to authenticate and authentication methods.
Selecting the template that you want to authenticate
Click Select to set the templates that you want to authenticate.
All templates need to be authenticated by default. If you lock the template, it means that the template does not need authentication.
Note:
1. Unlike the directory permissions, in Template Authentication, everyone's BI templates are displayed in a parallel structure rather than in a hierarchical structure.
2. It is not recommended to create a first-level directory named “reportlets” under the WEB-INF/reportlets folder of the project, otherwise the template tree will not be able to load.
Selecting AUTH Method
Admin can select AUTH Method. The setting of three AUTH Methods is as follows:
1. Authentication user password only
2. Role Permission Authentication
3. Digital Signature Authentication
