User Manager

Double-click the UserService for the User Manager (default view when you have admin-Write access), as shown in Figure 287.

Figure 287. UserManager is table based view

Rows in the User Manager table represent existing users, where you can edit by either double-clicking a single user, or clicking to select one or more users and then clicking the Edit button.

By default, a row for a disabled user is colored grey; for an “expired” user is colored orange; and for a “locked out” user is colored red.

As in other table-based manager views, you can select multiple rows (users) for edit. This can be useful for a mass change to a property like Facets or Web Profile (or most recently, “Force Reset Password”). However, be careful when doing multiple user edits of things like Permissions and Passwords.

See subsectionsNetwork user notes Lockout notes and Network user notes for additional information about working in a station’s User Manager.

To add a new user, click the New button. This produces the New User dialog, as shown in Figure 288.

Figure 288. New (user) dialog

You can create multiple users by typing in a number in “Number to Add.” When you click OK, the Add dialog includes that number of user rows in the top table (Figure 289).

Figure 289. Adding multiple users

As needed, click to highlight a single user row before entering unique user properties such as User Name, Full Name, Permissions, and so on. For properties you wish to enter identically for all users (for example, Facets), hold down Shift and click to select all user rows, then enter property value.

For a listing of all the User properties, see User. Note two new User properties (in AX-3.7) relate to password handling. See About password expiration and reset for related details.

When you click OK, the user(s) are added with the property values you entered. Users appear as rows in the UserManager, and as child components under the UserService container.

Lockout notes

If you have lockout enabled in the UserService properties, a user will be locked out after several unsuccessful attempts to login (login using their user name, but with incorrect password). A locked-out user is indicated with a red row in the User Manager, as shown in Figure 290.

Figure 290. Locked out user is indicated by red

The User component that represents each user has a boolean “Lock Out” slot that provides read-only status of whether that user account is currently locked out (true) or not (false). If needed, you can link it to other logic in the station.

If locked out, a user will be unable to login into the station until the lockout period expires, as specified in the UserService. Also during a lockout, any attempted login activity for that user will not appear in the station’s AuditHistory (see AuditHistory station login activities). After the lockout period expires, the user displays in the UserManager as normal.

As administrator, be aware that each user has an action “Clear Lock Out,” that you can invoke to clear any lockout in progress. Access this command with a right-click on a user, either selected in the Nav tree or in the UserManager, as shown in Figure 291.

Figure 291. Clear lockout action for any user

Network user notes

When a network user is replicated (sync'ed) to a “user receiving” station, it is accessible in that station's User Manager just like any local “non network” user. In earlier NiagaraAX releases, this could be confusing because configuration properties appeared to be writable in user edits from User Manager.

However, any changes made to such a proxied network user (received from another station) were overwritten upon the next user synchronization from the source station. Only by looking at the property sheet of an (incoming) network user was it obvious that properties were read-only. This applies to both the source-user derived properties (most properties) as well as the “local override” properties from the (local) User Prototypes.

Starting in AX-3.7, note that proxied network users now appear read-only when accessed from the User Manager (as shown in Figure 292) as well as from their property sheet.

Figure 292. Edit dialog from User Manager for a proxied network user (properties read-only)

In addition, note that the property sheet for a proxied user includes additional properties (near the bottom) useful in determining the original source of the user. See Figure 293.

Figure 293. Special status properties in property sheet for proxied network user

syncExt (containing Source Station) -- Shows the ord to the NiagaraStation that proxies the station with the source User.

In previous NiagaraAX builds, an additional “Version” property appeared, now (by default) a hidden slot. It holds the last sync timestamp in milliseconds—which is data used in the synchronization process.