Skip to content

Configuring User Account Lock Settings

This guide explains how to configure user account lock settings for Privacera Self-Managed and Data Plane environments. These settings define:

  • The number of failed login attempts allowed before a user account is locked
  • The duration for which the account remains locked before it is automatically unlocked

Configure the Account Lock Threshold

Use this setting to define the maximum number of consecutive failed login attempts allowed before an account is locked.

Default Value: 5

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

Example Configuration:

YAML
1
PRIVACERA_PORTAL_MAX_LOGIN_FAILED_ATTEMPT: 5

Configure the Account Lock Duration

Use this setting to specify how long a locked account remains inaccessible before it is automatically unlocked.

Default Value: 900000 (15 minutes, in milliseconds)

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

Example Configuration:

YAML
1
PRIVACERA_PORTAL_LOCK_TIME_DURATION: 900000  # 15 minutes in milliseconds

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. Copy the sample-vars if they are not already present in the custom-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

  8. Restart the portal service if needed.