Table of Contents

Search

  1. About the Data Vault Administrator Guide
  2. Introduction to the Data Vault
  3. Data Vault Service Startup and Shutdown
  4. Data Vault Configuration
  5. Data Vault SSL Setup
  6. Data Vault ODBC Setup
  7. Data Vault Administration
  8. Data Repartitioning
  9. Partial Data Vault Copy
  10. Archived Data Migration
  11. Data Validation
  12. Bulk File Uploader
  13. Data Vault Administration Tool
  14. Data Vault Logs
  15. User Account Privileges
  16. ssasql Command Line Program
  17. Data Vault Audit Log
  18. Appendix A: Sample Configuration Files

Data Vault Administrator Guide

Data Vault Administrator Guide

Data Vault Passwords

Data Vault Passwords

You can configure optional policies for the user passwords used to access the Data Vault, either through the Data Vault SQL Tool or ODBC/JDBC clients. Select and configure the policies that you want to enforce based on company IT security policies. When a user changes their Data Vault password, they must separately update the password in the ILM repository.
The following Data Vault password policies are available:
Minimum password length
Specifies the minimum number of characters that a user's Data Vault password must contain.
Password complexity
When enabled, the password used to access Data Vault must contain at least one upper-case letter and at least one of the following special characters: @ # _ = , . ? ~ { }
Password duration
Requires a user to change their Data Vault password after a certain number of days.
Password blacklists
Prevents a user from re-using a specified number of previous passwords.
To enable a password policy, you must add the corresponding policy parameter to the [SERVER] section of the ssa.ini file. For more information, see the topic "SERVER Section" in the chapter "Data Vault Configuration."
The following characters are valid characters for a Data Vault password:
  • Upper and lower-case letters A-Z
  • Numbers 0 through 9
  • Special characters: @ # _ = , . ? ~ { }
Do not use the asterisk (*) character in the password.
Users can change a password themselves, or the DBA user can change a password for another user. The DBA user password never expires, and has a maximum of 30 characters.

Data Vault Passwords in the ILM Repository

When a Data Vault password expires, users must first update the password in Data Vault and then separately update the password in the ILM repository. If a user does not update their Data Vault password in the ILM repository, they are unable to connect to Data Vault from Data Archive. They will not be able to browse data, retire data, create a target connection, or perform other operations involving Data Vault.
You can update a Data Vault password in the ILM repository with the "PasswordChangeEnv.bat" or " PasswordChangeEnv.sh" utilities, which are available in the
optional
directory of the Data Archive installation. You can also use the utilities to update the password for the Data Vault connection by giving the connection name and password.
If you have enabled SSL in Data Archive, you must also enable SSL in the PasswordChangeEnv.sh or PasswordChangeEnv.bat utilities. Add the trust store parameter to the file in same manner as the
startApplimation.sh
or
startApplimation.bat
files. Open PasswordChangeEnv.sh or PasswordChangeEnv.bat in any text editor and add the following information:
-Djavax.net.ssl.trustStore=<full path and name of .jks truststore file> -Djavax.net.ssl.trustStorePassword=<password of .jks file>
For example:
java -Dfile.encoding=UTF-8 -Djavax.net.ssl.trustStore=/data/idvuser/Jenkins_slave/workspace/644/DA/irs11ilm02.jks -Djavax.net.ssl.trustStorePassword=password com.applimation.util.RepositoryDatabaseUserPasswordChange $location
To change a Data Vault password or a Data Vault password in the ILM repository, first configure the
PasswordChangeSampleProperty.properties
file, which is also available in the
optional
directory of the Data Archive installation. When you configure the file you provide the ILM repository name, username, and new Data Vault password. You can also designate a separator value if you are providing multiple user names and passwords. You can choose any value for the separator as long as it is not used in the password. For example:
amhome.values.separator=## amhome.rep.names=demo2_expdays2 amhome.rep.usernames=demo1 amhome.rep.newpasswords= D@@123
After you configure and save the
PasswordChangeSampleProperty.properties
file, run the PasswordChangeEnv.bat or PasswordChangeEnv.sh utility, depending on the operating system. The utility asks for the full path of the properties file that you configured, and returns either an error or success message.

0 COMMENTS

We’d like to hear from you!