Skip to content

Configuring Portal Password Policy

This guide explains how to configure the password length policy for users of the Privacera Self-Managed Portal.

The password policy applies to Privacera Portal native users, including the padmin user. A valid password must:

  • Have a length between the configured minimum and maximum (default 8 to 20 characters)
  • Contain at least one uppercase letter
  • Contain at least one digit

Lowercase letters and special characters are allowed but not required.

The policy is checked only when a password is created or changed. Existing users whose passwords are shorter than a newly configured minimum can still log in, and must meet the new policy the next time they change their password.

Configure the Minimum Password Length

Use this setting to define the minimum number of characters required in a password.

Default value: 8

Configuration file: vars.portal.yml (via Privacera Manager)

Example configuration:

YAML
1
PORTAL_PASSWORD_MIN_LENGTH: "12"

Configure the Maximum Password Length

Use this setting to define the maximum number of characters allowed in a password.

Default value: 20

Configuration file: vars.portal.yml (via Privacera Manager)

Example configuration:

YAML
1
PORTAL_PASSWORD_MAX_LENGTH: "20"

Note

  • If you set only PORTAL_PASSWORD_MIN_LENGTH, the maximum stays at the default of 20. To use a minimum greater than 20, also increase PORTAL_PASSWORD_MAX_LENGTH.
  • The maximum supported length is 72. A larger value is capped at 72.
  • If the minimum is greater than the maximum, or a value is not a positive number, Privacera Portal logs a warning and uses the default policy (8 to 20).

Apply Configuration Changes

After updating the configuration:

  1. SSH into the instance where Privacera Manager is installed.

  2. Navigate to the config directory with the following command:

    Bash
    1
    cd ~/privacera/privacera-manager/config

  3. If vars.portal.yml is not already present in the custom-vars directory, copy it from the sample-vars directory by running the following command:

    Bash
    1
    cp -n sample-vars/vars.portal.yml custom-vars/vars.portal.yml

  4. Open the vars.portal.yml file in a text editor:

    Bash
    1
    vi custom-vars/vars.portal.yml

  5. Add or update the configuration properties as shown above.

  6. Save and close the file.

  7. Update the Privacera Manager platform instance:

    Step 1 - Setup which generates the helm charts. This step usually takes few minutes.

    Bash
    1
2
    cd ~/privacera/privacera-manager
./privacera-manager.sh setup
    Step 2 - Apply the Privacera Manager helm charts.
    Bash
    1
2
    cd ~/privacera/privacera-manager
./pm_with_helm.sh upgrade
    Step 3 - (Optional) Post-installation step which generates Plugin tar ball, updates Route 53 DNS and so on. This step is not required if you are updating only connector properties.

    Bash
    1
2
    cd ~/privacera/privacera-manager
./privacera-manager.sh post-install

The new policy takes effect after the Privacera Portal service restarts as part of the update.

Where the Policy Applies

Area Behavior
Settings > User Management (add user, edit user, change password) The New Password field shows the configured length in its tooltip and validation message, and the Portal API rejects passwords that do not meet the policy.
Access Management > Users/Groups/Roles (add or change a Ranger user password in Privacera Portal) The New Password field uses the same configured length and shows the same message.
PORTAL_PADMIN_PASSWORD in Privacera Manager During installation, the Privacera Manager pre-check shows a warning if the password is shorter than PORTAL_PASSWORD_MIN_LENGTH. The warning does not stop the installation.