[Index]

Model: data/CredentialPolicy

Credential Policy

Full HTML Help

Overview

Credential policies are sets of rules that define user sign-in behavior at various levels of the hierarchy. For example, to facilitate user account security, VOSS Automate authenticates user sign-in credentials before allowing access to the system. Additionally, administrators can configure settings for events such as failed sign-in attempts and lockout duration.

Credential policies can be applied at any hierarchy level. A credential policy applied at a particular hierarchy defines allowed user sign-in behavior at that hierarchy.

Related Topics

• Introduction to Hierarchies
• Authorized Admin Hierarchies and Roles

Default credential policy

While credential policies are not mandatory at specific hierarchy levels, a default credential policy is defined at the sys.hcs level.

Administrators at lower levels can copy and edit the default policy, if required, or they can save the default credential policy at their own hierarchy level so that it can be applied to users at that level.

Inherited credential policies

If an administrator at a specific level of the hierarchy has not created a credential policy at their hierarchy level, the credential policy is inherited from the closest level above.

If a Provider administrator has defined a credential policy, but a Customer administrator has not defined a credential policy, the customer hierarchy automatically inherits the credential policy from the Provider level.

Custom credential policies

A different credential policy can be defined for each user.

For each administrator user where IP address throttling (sign-in Limiting per Source) is required, a credential policy should be manually created and assigned. This credential policy must have an IP address, and username and email throttling enabled.

Related Topics

• Deploy a Customized Credential Policy

Credential policies, SSO authenticated users, and LDAP-synced users

Credential policies are not applicable for SSO authenticated users. For LDAP synced users, only the session timeouts are applicable.

Assign a credential policy to a user

Full HTML Help

This procedure assigns a credential policy.

Typically, a user inherits a credential policy from the nearest hierarchy node, at or above their location, wherever a default credential policy is defined. However, you can explicitly assign a credential policy to a user.

1. Log in as provider, reseller, or customer administrator.

2. Go to the Users page.

3. Click the user that you want to assign a credential policy to.

4. On the Account Information tab, from the Credential Policy drop-down, choose a credential policy to assign.

   The menu contains all the credential policies available at or above the user's node in the hierarchy.

6. Click Save.

Assign a credential policy to an administrator

Full HTML Help

This procedure assigns a credential policy to an administrator.

Typically, an administrator inherits a credential policy from the nearest hierarchy node at or above their location, wherever a default credential policy is defined. However, you can explicitly assign a credential policy to an administrator.

1. Log in as provider, reseller, or customer administrator.

2. Go to the Admins page.

3. Click the administrator that you want to assign a credential policy to.

4. On the Account Information tab, from the Credential Policy drop-down, choose a credential policy to assign.

   The menu contains all the credential policies available at or above the administrator's node in the hierarchy.

6. Click Save.

Customized credential policy

Full HTML Help

Overview

A default credential policy called HcsCredentialPolicy ships with Automate. However, you can deploy a customized credential policy at a provider, reseller, or customer hierarchy node.

When you set a customized credential policy as the default credential policy at a hierarchy node, all users and admins at or below that hierarchy node are subject to the customized credential policy, except for any users or admins that are explicitly assigned a different credential policy.

Related topics

• Credential Policies

Credential policy inheritance

Unless explicitly assigned a credential policy, users and admins are subject to the default credential policy set at a hierarchy node at or above their location. The default credential policy for the hierarchy node closest to the user or admin location is used. If no customized credential policies are deployed, all users and admins are subject to the HcsCredentialPolicy credential policy, which is the default credential policy at the sys.hcs level.

Deploy a customized credential policy

1. Log in as provider, reseller, or customer administrator.
2. Set the hierarchy path to the node where you want to deploy a customized credential policy.
3. Go to the Credential Policy page.
4. Either clone the HcsCredentialPolicy credential policy, or add a new credential policy:
   • To clone the HcsCredentialPolicy policy, click HcsCredentialPolicy, then click Action > Clone.
   • To add a new credential policy, click Add. The credential policy settings default to the settings for HcsCredentialPolicy.
5. Provide a name for the credential policy.
6. Modify the credential policy settings as needed.

Acceptable special characters are:

` ~ ! @ # $ % ^ & * ( ) - _ = + [ { ] } | \\ : ; ' " , < . > / ?

7. Click Save.

   Note

   If a user is already logged in when the credential policy is changed, changes do not take effect until the user logs out and logs in again.

8. Go to Default Credential Policy.

9. Provide a name for the Default Credential Policy at this hierarchy node.

10. From the Credential Policy drop-down, choose the credential policy you just cloned or added.

11. Click Save.

    Every user and administrator at or below the hierarchy node is now subject to the default credential policy, unless the user or administrator was explicitly assigned a different credential policy.

Defines rules the govern management of user credentials.

Model Details: data/CredentialPolicy