Creating Encrypted Files For The Security Infrastructure - Symantec Veritas Cluster Server Installation Manual

Linux for ibm power
Hide thumbs Also See for Veritas Cluster Server:
Table of Contents

Advertisement

Creating encrypted files for the security infrastructure

If the output displays the following error, then the account for the given
authentication broker is not created on this root broker:
"Failed To Get Attributes For Principal"
Proceed to step 3.
3
Create a principal account for each authentication broker in the cluster. For
example:
venus> # vssat addprpl --pdrtype root --domain \
root@venus.symantecexample.com --prplname galaxy \
--password password --prpltype service
You must use this password that you create in the input file for the encrypted
file.
Create encrypted files (BLOB files) only if you plan to choose the semiautomatic
mode that uses an encrypted file to configure the Authentication Service. The
administrator must create the encrypted files on the root broker node. The
administrator must create encrypted files for each node that is going to be a part
of the cluster before you configure the Authentication Service for VCS.
To create encrypted files
1
Make a note of the following root broker information. This information is
required for the input file for the encrypted file:
hash
root_domain
2
Make a note of the following authentication broker information for each node.
This information is required for the input file for the encrypted file:
Preparing to configure the clusters in secure mode
The value of the root hash string, which consists of 40
characters. Execute the following command to find
this value:
venus> # vssat showbrokerhash
The value for the domain name of the root broker
system. Execute the following command to find this
value:
venus> # vssat showalltrustedcreds
Preparing to install VCS
35

Advertisement

Table of Contents
loading

This manual is also suitable for:

Veritas cluster server 5.0 update 3

Table of Contents