Creating a Password File for the Administration Server73WARNINGThis password is stored in clear text within the password file, so its usage represents asignificant security risk. Do not use a password file if the server is running in an unsecuredenvironment.The password file must be in the same directory where the other key and certificate databasesfor Directory Server are stored. This is usually the main configuration directory, /etc/dirsrv/slapd-instance_name. The file should be named pin.txt.Include the token name and password in the file. For example:Internal (Software) Token:secretFor the NSS software crypto module (the default software database), the token is always calledinternal.The PIN file should be owned by the Directory Server user and set to read-only by the DirectoryServer user, with no access to anyone other user (mode 0400).6.4.2. Creating a Password File for the Administration ServerLike the Directory Server, the Administration Server can use a password file during login when TLS/SSL is enabled.WARNINGThis password is stored in clear text within the password file, so its usage represents asignificant security risk. Do not use a password file if the server is running in an unsecuredenvironment.1. Open the Administration Server configuration directory, /etc/dirsrv/admin-serv.2. Create a password file named password.conf. The file should include a line with the tokenname and password, in the form token:password. For example:internal:secretFor the NSS software crypto module (the default software database), the token is always calledinternal.The password file should be owned by the Administration Server user and set to read-only by theAdministration Server user, with no access to any other user (mode 0400).NOTETo find out what the Administration Server user ID is, run grep in the AdministrationServer configuration directory:cd /etc/dirsrv/admin-serv