Local user configuration settings
The following table provides a brief explanation of the User object configuration settings for creating local user accounts.
| Field | Description |
|---|---|
|
Login Name |
Name the user will use to log in to the administration console. This is a mandatory field. |
|
First Name |
User’s first name. |
|
Last Name |
User’s last name. |
|
|
User’s email address. This field is important for email notifications. |
|
Password/Confirm |
Password required for the user to log in to the administration console. NOTE Local passwords are not stored in clear text. The password must meet the Private Key Export rule for the certificate. This is the rule set on the certificate's policy folder. If the folder doesn't set a rule, the default Private Key Export rule is used. . IMPORTANT Spaces at the start or end are kept as part of the password.. To open the private key file later, you must type exactly the same password. For more information, see Global password rules. NOTE You can configure password age notifications for local identities in Palo Alto Networks Trust Protection Foundation. For more information, see User object. |
|
Master Admin |
The Master Administrator role grants the user all permissions to all objects in the Trust Protection Foundation Administration Console. This role is equivalent to the Local:Admin user. You must be a Master Administrator to assign this role to other administrators. WARNING! Use this role with extreme caution. It gives the user full permissions to every object in the Trust Protection Foundation database, including certificates, private keys, and credentials. WARNING! You cannot hide objects from a user with the master admin role. |
|
Allow Web SDK Access |
Gives the current administrator access to the Web SDK REST APIs. If this option is not selected, the user will not be able to log in through the Web SDK. You can disable permissions enforcement for all users who authenticate into Trust Protection Foundation. |