Description of scene requirements
In order to enhance the mobile login mechanism verification, to ensure the security of data. The reporting tool Finereport provides the ability to bind mobile devices, and each system user needs to be authorized by the administrator to bind the user's mobile device to the system when using the mobile connection, assuming the administrator has not authorized the device. You cannot log on.
Note: License to mobile device. Need to be used in conjunction with users, that is, users can only use a fixed one or several devices to log on to the system. Assume that you are logged on with another device. However, the device is not authorized, but also can not login, assume that a search authorized device on the switch account login. You also need to authorize the switch account again.
Another: A new project, when the first user logs on using a mobile side. No administrator authorization is required. For example, the user Anna is the entire project first user to use the mobile login, then Anna uses this device does not need to authorize, can connect directly. Other users ' devices will need to be authorized.
First, mobile device binding step
prepare a new Webreportproject. Start the built-in server.
1. Turn on mobile device bindings
FineReport the mobile device bindings feature is turned off by default. To open before use, enter http://localhost:8075/WebReport/ReportServer?op=fsin the browser address bar on the PC side. Log in with an administrator account, click Manage Systems > Mobile Platforms > Device Bindings to turn on mobile device bindings, for example:
2, the first device login
use an administrator account on a single machine to connect to the project and log in directly without having to authorize the device. The administrator logs on to the data decision system on the PC, into the management System > mobile Platform > Device Bindings . You can see the MAC address of a device on an authorized device that shows an administrator user-bound , for example:
Note: Users who log on to the system for the first time are not necessarily administrators.
3, the second device login
after the first device login system, no matter what the user, the second and later devices on the mobile login system need administrator authorization, on another device, according to the server configured to join the server , using the same account login, click Login, A warning box will pop up:
at this point. The administrator refreshes the data decision system on the PC side to see a new record is added to the unauthorized device . Indicates that the user is logged on to the system on another device and needs to authorize the device.
Click the Middle button to move an unauthorized device to the authorized Devices Panel, which is authorized for unauthorized devices:
At this time Sign in again on the mobile side. will be able to log in, and no matter what system users on the device use the mobile Access system, there is no need to re-authorize.
4. Switch Users
on the second device Sign Out , replace a user to continue to log on to the system, and found that the device is not authorized dialog box, requires administrator authorization, after the administrator authorized. You can see it in Management systems > Mobile Platforms > Mobile device Bindings > Authorized Devices . One more User:
Second, mobile device authorization revocation
In practical applications. A user basically binds only one device, assuming that the device is lost or damaged before using another device, then. Suppose a user is often using a device that is missing, and to bind the mobile end to another device, but the lost device is bound to the system. This can cause data to be unsafe.
The Finereport provides device management capabilities. That is, when multiple devices are bound by the same user at the same time, the user simply needs to log on to the system on a discretionary device to revoke the authorization rights of other devices.
In addition to the Administrator removing the authorized device directly on the PC side. The Finereport also provides device management capabilities. That is, when multiple devices are bound by the same user at the same time, the user simply needs to log on to the system on a discretionary device to revoke the authorization rights of other devices.
1. Equipment Management
The example shown above shows that an administrator user has logged on to two devices, Authorized Devices The panel is tied to the MAC address of two devices , and then we're logging on to the ipad device to revoke the iphone device's licensing rights.
log on to the system on the mobile side. Click the option button in the upper-right corner to select device bindings , for example:
in the Device Management interface to see all the devices that the user is bound to. The current device is not operational, other devices are operable, for example:
Swipe the button after the device name. Revoke the user's authorization for the device, for example, by:
At this point, the administrator logs on to the system on the PC, enters the management System > mobile Platform > Device Bindings , and the authorized devices panel can see that the bundled devices under AA users are only one left, The revoked device is again returned to the unauthorized device panel, for example:
2, PC -side directly Delete
users who have access to mobile platforms, usually administrators, log on to the system at the PC, enter Management systems > Mobile Platforms > Device Bindings , and can remove unauthorized devices directly and the Authorized Devices the following devices. For example, with:
How mobile device bindings and cancellations are made on the report mobile side