Users

Prev Next

The first time you connect to a new Pathfinder Core PRO, you choose the password for the Admin user (see First-Time Setup in the System article). After that, log in with the username Admin and that password.

To change the password or manage users, click the System > Users link on the navigation bar.

The page has two lists:

  • Users: everyone who can log in, with the Security Group each one belongs to and whether they have Emergency Access.

  • Security Groups: the sets of permissions that users are given. The Type column shows whether a group is an Administrator group or a User group.

A user's rights come from their security group. To give several people the same rights, put them in the same group; to change those rights, edit the group once.

Users

Click edit to change a user's password or click Add + to add users to the system. Use the trash icon to delete users from the system.

Field

Description

User Name

The name used to log in. Names must be unique, ignoring upper and lower case: operator and Operator cannot both exist.

Password

Type the password twice. It cannot be empty or contain spaces.

Emergency Access

Lets this user log in through the emergency login page when LDAP authentication is unavailable. See Emergency Access in the Security section of the System article. The checkbox is disabled on the ClusterAdmin user, so its emergency access cannot be changed.

Security Group

The group whose rights this user has.

Can Lock Routes, Route locks do not apply

Shown for compatibility. The user's security group decides both; set them on the group.

After you create a new user, that user's credentials can be used to log in to the Pathfinder Core PRO web pages or to PathfinderClient, PathfinderMini, or PanelDesigner.

The system will not let you delete or change the last user with administrator rights, as there would then be no way to administer the system. (The ClusterAdmin user used by clustering does not count.) The system asks for confirmation before removing the Admin user's administrator rights.

Warning: Never remove administrator rights from all of the users you can log in as. You could lose access to the system, and support would then need access to the operating system to reset it.

Security Groups

Two groups always exist and cannot be deleted or renamed: Administrator and user. Click Add + under the Security Groups list to add a group, edit to change one, or clone to copy one under a new name (by default the old name followed by _Copy). A group cannot be deleted while users still belong to it.

Field

Description

Group Name

The group's name. When LDAP authentication is used, this is also the name of the LDAP or Active Directory group it stands for.

Is Administrator

Members are administrative users who have access to everything. The Menus and Allowed APIs sections are hidden for administrator groups.

Can Lock Routes

Members can lock and unlock routes.

Route locks do not apply

Members can change routes even when they are locked.

For groups that are not administrator groups, click the arrows next to Menus and Allowed APIs to expand them and specify the group's rights. By default, a new group sees all navigation menu items but has no rights in the API, so most or all of the menu items will not populate with any data.

The Menus section defines which navigation bar menu items are available to members of the group.

The menus listed are the same as in the navigation bar on the web page. Items set to hidden no longer appear in the user's navigation bar.

The Allowed APIs section defines in much more detail what members may access via the web pages, port 9600 login, and the client applications:

Each item in the displayed list has several options:

  • Inherit means that branch in the tree inherits the rights of the parent branch. For root-level objects such as Logic Flows, the inherited state is No Access. No Access explicitly denies access to that branch.

  • Display allows the user to display the resource but not change or use it. For example, to let the user view the route states of a router but not make any route changes, select display for the router access.

  • Change/Use allows the user to do normal operations with the resource but not change the definition of the resource. For example, in the case of routers, selecting change/use lets the user make route changes on the router but not add sources or destinations to the router.

  • Full access gives the user complete control over the resource, including the ability to add to or delete the resource. This is the equivalent of administrator rights to the resource.

By default, branches below a specific branch inherit the parent's properties. So, if you set the Routers branch to display, all routers will be displayed. You can then set no access on routers you do not want the user to see and/or Change/Use access to routers you want them to be able to use.

Upgrading From 1.10

Versions before 2.0 stored rights on each user. When a system is upgraded, each user is given a security group of their own, named after the user, with the same rights they had before. Users with administrator rights are given an administrator group named after them. Nothing changes for the people using the system. Afterwards you can move users with the same rights into one group and delete the groups you no longer need.

Important Note: Take a backup before upgrading. Rights changed through security groups after the upgrade are not seen by an older version if you return to it.

Security Groups and LDAP

When LDAP authentication is enabled (see the Security section of the System article), a user who logs in with their directory credentials gets the rights of the security group whose name matches one of their LDAP or Active Directory groups. The match ignores upper and lower case. If several groups match, the user gets the most permissive combination. A user who is not a member of any matching group is refused.

For example, to give the members of an Active Directory group called PcpAdmin administrator rights, add a security group named PcpAdmin with Is Administrator ticked. In 1.10, this needed a placeholder user named after the directory group. In 2.0, no user is needed.

IP Address White Lists

Attempts to access the system from the specified IP address will bypass the normal login process and use the permissions of the user assigned to the white list entry. While using this option weakens security somewhat (IP addresses can be spoofed), it allows systems that may not usually have a keyboard attached to reconnect without requiring a login. To add a white list entry, click the Ip Address White List link on the Users page.

Click Add + to add a new white list entry or the Return to Users link to exit the white list configuration page.

Each entry requires a range of IP addresses specified using CIDR format. For example, the entry above represents a single IP address. For help figuring out the correct format, there are numerous CIDR calculators available on the internet (e.g. http://jodies.de/ipcalc). You must also specify a Security User from the users list. That user's permissions apply to anyone who accesses the system from that IP address. A Description (up to 128 characters) is optional and is a good place to note what the address belongs to. Once an IP address range is specified, it is not currently possible to log in from that IP address as a different user than the one specified.

Warning: Be careful not to specify your entire internal network along with a non-Admin user, or you could lose the ability to configure Pathfinder Core PRO. That can require working with support to correct. While you can use the CIDR structure to specify a range, this feature is intended to let unattended systems such as wall displays automatically display panels without user intervention. It is not intended to be used to bypass all security credentials.