One Identity Safeguard for Privileged Passwords 8.0 LTS

It is the responsibility of the Asset Administrator or the partition's delegated administrator to configure the rules Safeguard for Privileged Passwords uses to reset account passwords.

IMPORTANT: Passwords for accounts associated with a password sync group are managed based on the profile change schedule and processed via the sync group. If synchronization fails for an individual account in the sync group, the account is retried multiple times and, if failing after that, the sync task halts and is rescheduled. The administrator must correct the cause of the failure for the sync task to continue. For more information, see Password sync groups..

Navigate to Asset Management > Profiles > View Password Profile Components > Change Password.

To add a password reset schedule

Click Add to open the Change Password Settings dialog.
Enter a Name of up to 50 characters for the rule.
Enter a Description of up to 255 characters for the rule.
Select a partition using the Browse button.
Optionally, complete any of these settings:
- Change Passwords Manually. For more information, see How do I manage accounts on unsupported platforms..
- Change the password even if release is active: Select this option to allow a password change even when a password release is active.
- Require current password: Select this option to require a current password.
- Suspend account when checked in: Select this option to automatically suspend managed accounts that are not in use. That is, the account on a managed asset is suspended until a request is made for it through Safeguard for Privileged Passwords, at which time Safeguard for Privileged Passwords restores the account. Once the request is checked in or closed, the account is again suspended.
  
  Click the supported platforms link to display a list of platforms that support this feature.
- Reschedule for unscheduled password change: Select this option to reset the password schedule when a password is manually changed. For example: a password reset is scheduled to occur every 10 days, but on day 8 the password is manually changed. Due to this manual reset, the schedule will restart so that the next password reset will occur in 10 days rather than keeping the original scheduled reset (which would have been in 2 days).
NOTE: All options listed below are supported only on Windows platforms. Expand the Windows Only section to view these options.
- Update service on password change (Windows Only): For Windows services that are configured to run as a local managed account or a dependent AD account on an asset, select this option to ensure that the password change is also applied to each service the account runs. If the service is running as a dependent AD account, the windows asset and the dependent Active Directory account must be in the same profile.
- Restart service on password change (Windows Only): For Windows services that are configured to run as a local managed account or a dependent AD account on an asset, select this option to ensure that there is an automatic restart after the password is changed. For a local account, the profile assigned to the account is used. For an AD account, the profile assigned to the asset is used.
- Update IIS app pool on password change (Windows Only): For IIS App pools that are configured to run as a local managed account or a dependent AD account on an asset, select this option to ensure that the password change is also applied to each IIS App pool the account runs. If the service is running as a dependent AD account, the windows asset and the dependent Active Directory account must be in the same profile.
- Update COM+ on password change (Windows Only): For Com+ applications that are configured to run as a local managed account or a dependent AD account on an asset, select this option to ensure that the password change is also applied to each COM+ application the account runs. If the service is running as a dependent AD account, the windows asset and the dependent Active Directory account must be in the same profile.
- Update task on password change (Windows Only): For scheduled tasks that are configured to run as a local managed account or a dependent AD account on an asset, select this option to ensure that the password change is also applied to each task the account runs. If the service is running as a dependent AD account, the windows asset and the dependent Active Directory account must be in the same profile.
(Only Linux, Unix, and Windows SSH platforms) (Optional) On the Dependent Systems tab, click Edit to configure a custom dependency that will run a command on an asset to perform custom updates when a password is changed for a dependent account. The following configuration options are available:
IMPORTANT: When configuring custom dependency commands, the following information should be kept in mind:
- Any valid command on the asset that is accessible to the service account can be configured to run as a dependency. NO VALIDATION will be performed by Safeguard on the command.
- You cannot discover services, or automatically configure dependencies on Linux/Unix.
- A directory account can be manually configured as a dependent account on Linux/Unix.
- If you add a directory account as a dependent account for a Linux/Unix asset, the asset's profile will determine the action (including any custom commands) to take when the AD account password changes.
- Local accounts are automatically dependent accounts if a custom dependency is configured in the account's password profile.
- For AD accounts, custom dependencies will only run after a successful password change; and will run on each Unix or Linux asset configured as a dependent asset, rather than on the AD asset.
- For AD accounts, any commands configured to run before a password change or after a failed password change will be ignored.
- Run custom command before password change: Select this option to configure a custom dependency that is run before a password change occurs on a dependent account.
  - Command: This is the command that will be run. It is a free format string that should identify the fully qualified path of the command to be run. It can contain tokens that will be resolved using the account details when the operation runs.
    
    You can use the Insert Command Token drop-down to add tokens to the field. For example, selecting AssetName will add %{AssetName}% to the Command field. The AssetName token will then be replaced when the operation is run on an asset.
  - Command Line Arguments: These are the arguments that will be passed on the command line. It can contain tokens that will be resolved using the account details when the operation runs. The command line arguments should be quoted appropriately (for example, an argument that contains a space must be quoted).
    
    You can use the Insert Command Line Argument Token drop-down to add tokens to the field. For example, selecting UserKey will add %{UserKey}% to the Command Line Arguments field.
  - Stdin Arguments: The is an ordered list of arguments that will be written to stdin when the command is run. Each string in the list will be written as a separate line and can contain tokens.
    
    You can use the Insert Stdin Argument button to open a dialog that allows you to enter a string value. You can also use the Insert Stdin Argument Token drop-down to select from a list of tokens that be included. For example, selecting DelegationPassword will add %{DelegationPassword}% as a string in the Stdin Arguments section.
  - Stop On Fail: When selected, the password change will not be run if the custom dependency command fails.
  - Log Command: When selected, the command to be run will be logged.
  - Log Command Arguments: When selected, the command line arguments will be logged.
  - Log Stdin Arguments: When selected, the arguments written to stdin will be logged.
  - Log Stdout: When selected, the output generated by the command will be logged.
- Run custom command after successful password change: Select this option to configure a custom dependency that is run after a successful password change on a dependent account.
  - Command: This is the command that will be run. It is a free format string that should identify the fully qualified path of the command to be run. It can contain tokens that will be resolved using the account details when the operation runs.
    
    You can use the Insert Command Token drop-down to add commands to the field. For example, selecting AssetName will add %{AssetName}% to the Command field.
  - Command Line Arguments: These are the arguments that will be passed on the command line. It can contain tokens that will be resolved using the account details when the operation runs. The command line arguments should be quoted appropriately (for example, an argument that contains a space must be quoted).
    
    You can use the Insert Command Line Argument Token drop-down to add commands to the field. For example, selecting UserKey will add %{UserKey}% to the Command Line Arguments field.
  - Stdin Arguments: The is an ordered list of arguments that will be written to stdin when the command is run. Each string in the list will be written as a separate line and can contain tokens.
    
    You can use the Insert Stdin Argument button to open a dialog that allows you to enter a string value. You can also use the Insert Stdin Argument Token drop-down to select from a list of tokens that be included. For example, selecting DelegationPassword will add %{DelegationPassword}% as a string in the Stdin Arguments section.
  - Log Command: When selected, the command to be run will be logged.
  - Log Command Arguments: When selected, the command line arguments will be logged.
  - Log Stdin Arguments: When selected, the arguments written to stdin will be logged.
  - Log Stdout: When selected, the output generated by the command will be logged.
- Run custom command after failed password change: Select this option to configure a custom dependency that is run after a password change fails for a dependent account.
  - Command: This is the command that will be run. It is a free format string that should identify the fully qualified path of the command to be run. It can contain tokens that will be resolved using the account details when the operation runs.
    
    You can use the Insert Command Token drop-down to add commands to the field. For example, selecting AssetName will add %{AssetName}% to the Command field.
  - Command Line Arguments: These are the arguments that will be passed on the command line. It can contain tokens that will be resolved using the account details when the operation runs. The command line arguments should be quoted appropriately (for example, an argument that contains a space must be quoted).
    
    You can use the Insert Command Line Argument Token drop-down to add commands to the field. For example, selecting UserKey will add %{UserKey}% to the Command Line Arguments field.
  - Stdin Arguments: The is an ordered list of arguments that will be written to stdin when the command is run. Each string in the list will be written as a separate line and can contain tokens.
    
    You can use the Insert Stdin Argument button to open a dialog that allows you to enter a string value. You can also use the Insert Stdin Argument Token drop-down to select from a list of tokens that be included. For example, selecting DelegationPassword will add %{DelegationPassword}% as a string in the Stdin Arguments section.
  - Report of Exit Status: When selected, the exit status will be reported to Safeguard for Privileged Passwords and the operation will be retried. When this option is not selected, Safeguard for Privileged Passwords will report success for the operation regardless of the result.
  - Log Command: When selected, the command to be run will be logged.
  - Log Command Arguments: When selected, the command line arguments will be logged.
  - Log Stdin Arguments: When selected, the arguments written to stdin will be logged.
  - Log Stdout: When selected, the output generated by the command will be logged.
On the Schedule tab, select Run Every to run the job along per the run details you enter. (If you deselect Run Every, the schedule details are lost.)
- Configure the following.
  
  To specify the frequency without start and end times, select from the following controls. If you want to specify start and end times, go to the Use Time Window selection in this section.
  
  Enter a frequency for Run Every. Then, select a time frame:
  - Minutes: The job runs per the frequency of minutes you specify. For example, Every 30 Minutes runs the job every half hour over a 24-hour period. It is recommended you do not use the frequency of minutes except in unusual situations, such as testing.
  - Hours: The job runs per the minute setting you specify. For example, if it is 9 a.m. and you want to run the job every two hours at 15 minutes past the hour starting at 9:15 a.m., select Runs Every 2 Hours @ 15 minutes after the hour.
  - Days: The job runs on the frequency of days and the time you enter.
    
    For example, Every 2 Days Starting @ 11:59:00 PM runs the job every other evening just before midnight.
  - Weeks The job runs per the frequency of weeks at the time and on the days you specify.
    
    For example, Every 2 Weeks Starting @ 5:00:00 AM and Repeat on these days with MON, WED, FRI selected runs the job every other week at 5 a.m. on Monday, Wednesday, and Friday.
  - Months: The job runs on the frequency of months at the time and on the day you specify.
    
    For example, If you select Every 2 Months Starting @ 1:00:00 AM along with First Saturday of the month, the job will run at 1 a.m. on the first Saturday of every other month.
- Select Use Time Windows if you want to enter the Start and End time. You can click Add or Remove to control multiple time restrictions. Each time window must be at least one minute apart and not overlap.
  
  For example, for a job to run every ten minutes every day from 10 p.m. to 2 a.m., enter these values:
  
  Enter Every 10 Minutes and Use Time Windows:
  - Start 10:00:00 PM and End 11:59:00 PM
  - Start 12:00:00 AM and End 2:00:00 AM
    
    An entry of Start 10:00:00 PM and End 2:00:00 AM will result in an error as the end time must be after the start time.
  If you have selected Days, Weeks, or Months, you will be able to select the number of times for the job to Repeat in the time window you enter.
  
  For a job to run two times every other day at 10:30 am between the hours of 4 a.m. and 8 p.m., enter these values:
  
  For days, enter Every 2 Days and set the Use Time Windows as Start 4:00:00 AM and End 8:00:00 PM and Repeat 2.
- (UTC) Coordinated Universal Time is the default time zone. Select a new time zone, if desired.
If the scheduler is unable to complete a task within the scheduled interval, when it finishes execution of the task, it is rescheduled for the next immediate interval.
Click OK.

Account Password Rules

Adding an account password rule

Table 159: Account Password Rules: Toolbar
Option	Description
Add	Add an account password complexity rule. For more information, see Adding an account password rule..
Delete	Remove the selected rule.
Edit	Modify the selected rule.
Refresh	Update the list of account password rules.
Search	To locate a value in this list, enter the character string to be used to search for a match. For more information, see Search box..

It is the responsibility of the Asset Administrator, or a partition's delegated administrator, to configure account password complexity rules.

IMPORTANT:

Some Unix systems silently truncate passwords to their maximum allowed length. For example, Macintosh OS X only allows a password of 128 characters. If an Asset Administrator creates a profile with an Account Password Rule that sets the password length to 136 characters, when Safeguard for Privileged Passwords changes the password for an account governed by that profile, the asset's operating system truncates the new password to the allowable length and does not return an error; however, the full 136-character password is stored in Safeguard for Privileged Passwords. This causes the following issues:

Check Password for that account will fail. When Safeguard for Privileged Passwords compares the password on the Unix host with the password in Safeguard for Privileged Passwords, they never match because the Unix host truncated the password generated by Safeguard for Privileged Passwords.
A user will not be able to log in to the Unix host account successfully with the password provided by Safeguard for Privileged Passwords unless they truncate the password to the allowable length imposed by the operating system.

Navigate to Asset Management > Profiles > View Password Profile Components > Account Password Rules.

To add an account password rule

Click Add to open the New Account Password Rule dialog.
Enter a Name for the account password rule (up to 50 characters).
Enter a Description for the account password rule (up to 255 characters).
Select a partition using the Browse button.
On the Password Rules tab, set the password requirements.
- Password Length: Set a range for the password allowable length from three to 255 characters. The default is 8 to 64 characters. The maximum length must be equal to or greater than the sum of minimum characters required in the following steps. For example, if the password must have two uppercase letters, two lowercase letters, and two numeric characters, the minimum Password Length must be six. Note that a diacritical letter is one character.
- First Character Type: Choose one of the following:
  - All: Alphabetical, numeric, or symbols
  - Alphanumeric: Alphabetical or numeric
  - Alphabetic: Only alphabetical characters
- Last Character Type: Choose one of the following:
  - All: Alphabetical, numeric, or symbols
  - Alphanumeric: Alphabetical or numeric
  - Alphabetic: Only alphabetical characters
- Repeated Characters: Choose one of the following:
  - Allow repeated characters: Any letters, numbers, or symbols can be repeated in any order, including consecutively.
  - No consecutive repeated characters: No letter, number, or symbol can be repeated after itself. You can restrict the number of consecutively repeated characters later by uppercase letters, lowercase letters, numbers, symbols, or a combination of those.
  - No repeated characters: All letters, numbers, or symbols can only be used once in the password.
- Allow Uppercase: Select to allow uppercase (capital) letters.
  - Require a Minimum of Uppercase Characters: Enter a number to identify the least number of uppercase letters required. To allow but not require uppercase letters, set this value at zero.
  - Limit Consecutively Repeated Uppercase Characters: If you allowed repeated characters earlier, select the check box to limit the number of consecutively repeated uppercase letters. You must enter a Maximum Allowed Characters value of one or more.
  - Exclude these Uppercase Characters: Enter any uppercase characters you want to exclude from the password. This field is case-sensitive.
- Allow Lowercase: Select to allow lowercase (small) letters.
  - Require a Minimum of Lowercase Characters: Enter a number to identify the least number of lowercase letters required. To allow but not require lowercase letters, set this value at zero.
  - Limit Consecutively Repeated Lowercase Characters: If you allowed repeated characters earlier, select the check box to limit the number of consecutively repeated lowercase letters. You must enter a Maximum Allowed Characters value of one or more.
  - Excluded these Lowercase Characters: Enter any lowercase characters you want to exclude from the password. This field is case sensitive.
- Limit Consecutively Repeated Alpha Characters: To set the number of repeated lowercase or uppercase letters combined, enter the Maximum Allowed Characters.
  
  For example, if you set the Max Allowed at 2 then you can not have more than two alphabet characters next to each other in the password. Using this example, Ab1Cd2EF is valid but AbC1d2EF is not because it has three alphabet characters in a row.
- Allow Numeric Character (0-9): Select to allow numeric characters in the password.
  - Require a Minimum of Numeric Characters: Enter a number to identify the amount of numbers required in a password. To allow but not require numbers, set this value at zero.
  - Limit Consecutively Repeated Numeric Characters: Select the check box to limit the number of consecutively repeated numeric characters. You must enter a Maximum Allowed Characters value of one or more.
  - Exclude these Numeric Characters: Enter any numeric characters you want to exclude from the password. This field is case sensitive.
- Allow Symbols (e.g. @ # $ % &): Select this check box to allow characters that are printable ASCII characters. These often include: ~ ` ! @ # $ % ^ & * ( ) _ - + = { } [ ] \ | : ; " ' < > , . ? /
  - Require a Minimum of Symbols: Enter a number to identify the least number of symbols required. To allow but not require symbols, set this value at zero.
  - Limit Consecutively Repeated Symbols: If you allowed repeated characters earlier, select the check box to limit the number of symbols that can repeat consecutively. You must enter a Maximum Allowed Characters value of one or more.
  - Set the following:
    - Valid Symbols: Select this option to enter allowable special characters. Enter the allowable symbols in the Symbol List text box.
    - Invalid Symbols: Select this option to enter prohibited special characters. Enter the prohibited symbols in the Symbol List text box.
Click Test Rule to check the rules set.
When the rules are complete, click OK.

Password sync groups

A password sync group is used to control password validation and reset across all associated accounts. The same password is used for one or more accounts associated with the same or different assets. For example, synchronized passwords can be used for accounts that support clusters or systems that sync between development, test, and production. An account can belong to only one password sync group. Multiple password sync groups can be added to a profile.

The profile change schedule is applied to the sync group. The sync group controls the tasks to change the passwords for the accounts in the sync group. Change tasks occur in the order of password sync group account priority. If synchronization fails for an individual account in the sync group, the account is retried multiple times and, if failing after that, the sync task halts and is rescheduled. The administrator must correct the cause of the failure for the sync task to continue.

If an account is associated with a profile with a daily check schedule and also associated with a password sync group, a mismatch on the daily check will trigger a task to set the account password to the current sync group password.

For more information, see Creating a password profile..

Password sync group account priority

When an account is added to a password sync group, the default priority is 0, which is the highest priority. Subsequent numbers are lower priority (for example, 0, 1, or 2, where 0 is the highest priority and 2 is the lowest). Priority determines the order in which account passwords are changed.

If all accounts have the same priority, they are synchronized simultaneously. When different priorities are set, accounts at the highest priority (for example, 0) are synchronized first. If priority 0 is successful, accounts at the next priority are synchronized.

If any account at a priority fails, the synchronization processing stops and the group is scheduled for synchronization retry. For example, a cluster of systems may have an admin account with the same password. If one primary system is set at priority 0 and the subordinates are set at priority 1, the password change on the primary must be successful before the passwords on the subordinates are changed. If the primary password change fails, the subordinates are unaffected, the cluster continues to function, password change is rescheduled, and the error is logged.

Navigate to Asset Management > Profiles > View Password Profile Components > Password Sync Groups.

Table 160: Sync Groups: Properties
Property	Description
Enable	If Enable is selected, the sync runs with the profile change schedule.
Status	The Status displays if all account passwords are in sync with the password sync group. The Status is if any password for any account within the sync group does not match the common password.
Name	The name of the password sync group.
Accounts	The number of accounts to synchronize with a common password.
Next Sync Date	The date the sync group password will be synchronized across all accounts.
Description	Information about the rule.

Use the following toolbar buttons to manage password sync groups.

NOTE: Changes made from the Password Sync Groups pane are reflected in the password sync groups in the profile. See Creating a password profile.

Table 161: Sync Groups: Toolbar
Option	Description
Add	Add a password sync group. For more information, see Adding a password sync group..
Delete	Permanently remove the selected password sync group.
View Details	Modify the selected password sync group rule.
Change Sync Group Password	Change the password for the selected sync group. All accounts in the password sync group synchronize with the new password.
Refresh	Update the list of password sync groups.
Search	To locate a value in this list, enter the character string to be used to search for a match. For more information, see Search box..

One Identity Safeguard for Privileged Passwords 8.0 LTS - Administration Guide

Adding change password settings

Account Password Rules

Adding an account password rule

Password sync groups

Password sync group account priority

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

One Identity Safeguard for Privileged Passwords 8.0 LTS - Administration Guide

Adding change password settings

Account Password Rules

Adding an account password rule

Password sync groups

Password sync group account priority