The Sedona User Manager view is the default view of the
“users” service component (in the service folder) of a Sedona Framework app (the sys:UserService component).
Starting in Sedona TXS-1.2, Sedona devices networked in a NiagaraAX station (SedonaNetwork or SedonaJen6lpNetwork) can optionally
have Sedona users centrally managed at the station level. This is done using a Sedona User Manager service component (SedonaUserManagementService), along with a special Sedona Device User Manager view on the Sedona network component. For details, see Sedona users and roles management.
This view provides a way to view, add, edit, and delete child users in the app. Properties of each user determine their app login credentials, as well as their Sedona component permissions
(across four groups), and sox provisioning permissions (across three different areas).
This view includes a User table and three User Manager buttons.
The table area lists each user on a separate row, summarizing in columns:
Username
Name of app user (7 characters maximum)
Group Permissions
Available permissions for that user among component groups 1-4, where:
Operator level permissions show as “r
” (read), “w
” (write), “i
” (invoke, action)
Admin level permissions show as “R
” (Read), “W
” (Write), “I
” (Invoke, action), “u
” (user)
Provisioning Permissions
Available sox provisioning permissions for that user among three areas, where:
Sedona app provisioning is “app
”, kit provisioning is “kits
”, and Sedona VM provisioning is “svm
”
The button is always available. An Add User dialog results (Figure 75).
Configuration fields in Add User dialog are as follows:
Username
Unique name of user, 7 alphanumeric characters maximum, and is case sensitive. Must begin with letter and have no spaces or punctuation, apart from underscore ( _ ).
Password
Login password for this user, case sensitive.
Confirm
Repeat of the same password for this user, case sensitive.
Group Permissions
Component permissions for the 4 different component groups can be enabled or disabled by clicking in the popup Permissions dialog, with two access levels: Operator and Admin (Figure 76).
If a component belongs to more than one group, the user has the highest of those different group permissions for that component.
Provisioning Permissions
Sox provisioning permissions for the 3 different areas of the platform can be enabled or disabled by clicking in the popup Permissions dialog (Figure 77).
The button is available when any one user (row) is selected. It produces an Edit User dialog that is similar to the Add User dialog (Figure 75), where changes can be made to any field except Username.
The button is available when any one user (row) is selected. It produces an Delete User confirmation dialog. If confirmed with , that child User component is deleted.
Copyright © 2000-2014 Tridium Inc. All rights reserved.