Applications
This section outlines possible applications of the DashBoard Server and URM. Your requirements may differ from what is presented.
Before You Begin
You can start your approach to configuring and managing users in DashBoard URM by asking the following questions:
1.
Will user information and permissions be defined by an external LDAP Server or will this information be managed internally by the DashBoard Server and URM?
2.
How will you define the purpose of an Administrator? For example, one Administrator only upgrades the software on devices and a second configures and manages the DashBoard Server and URM.
3.
4.
5.
6.
7.
8.
9.
How do the users need to access the devices in DashBoard? For example, will specific users need to change parameters frequently, view card information only, or have access to a select set of device parameters?
10.
11.
Types of Applications
If the DashBoard URM service derives user information from an external LDAP Server, such as the one that defines your corporate user data, users and/or roles is defined by that LDAP Server (including password authentication). However, if the DashBoard URM service is to be managed as an isolated database, there are three basic applications for DashBoard URM: open, closed, or custom.
Operating Tip — The Server Configuration menu enables you to select the system default settings to Allow or Deny for properties that have no permissions set all the way up the hierarchy.
For more information on configuring examples of a specific type of application and the steps required, refer to the applicable section in “Appendix A. Applications”.
Open Application
An open application assumes that all users are granted full permissions for all devices. An open application is useful in situations where the users require full access to all devices, or the majority of users will be assigned to a single role. In either of this situations, you can create user accounts and assign them to a single role (Basic Users), all with the same permissions.
Operating Tip — For an open application, consider setting your default permission to Allow in the Configure DashBoard URM tab.
This application may include one or more of the following:
Granting the Basic Users role full access to all devices while an Administrator account manages the permissions for all devices, the DashBoard Server, and the DashBoard URM.
Configuring all user accounts permissions to “Allow” at the highest levels of the hierarchy for the Default User and Basic User role. You would only deny specific permissions where required.
Closed Application
A closed application assumes that users are either restricted to read access only and have no permissions for any devices on the subnet. Specific devices, such as an openGear frame, may or may not be locked with a password. This application may include one or more of the following:
Operating Tip — For a closed application, consider setting your default permission to Deny in the Configure DashBoard URM tab.
Limiting the users access to all devices listed in the DashBoard client by setting permissions to “Deny” at the highest levels of the hierarchy for the Default User and Basic User role. You would only specify permissions where required.
Custom Application
A custom application assumes that each user is granted specific permissions and belong to one or more roles. A single user can belong to many roles, each role with specific permissions, and be allowed to access any number of devices. Each user account may have specific permissions that apply only to that account. The advantage to using roles is that an Administrator can update the permissions for that one role and the change automatically affects the individual users assigned to that role.
In a custom application, some users may have only read access, other users may have read/write access for specific devices, or other users may have a combination of permissions. The configurations can be as complex or as simplistic as you need. Keep in mind that permissions assignment can be a multi-layered where access can be granted based on the user type, the role(s) they are assigned, and the device(s) they work with.