credentials.conf.spec

This is an example of the spec file.

# Copyright (C) 2012 Splunk Inc. All Rights Reserved.
#
# This file contains possible attribute/value pairs for configuring encrypted credentials 
# storage in credentials.conf. This file is used in the Splunk App for VMware Forwarder Appliance.
#
# Note: use of credentials.conf is optional, usernames/passwords can be placed as plain text in
# engine.conf 
#
# To learn more about configuration files (including precedence) please see the documentation 
# located at http://www.splunk.com/base/Documentation/latest/Admin/Aboutconfigurationfiles

[default]
* This stanza contains the default credentials to be applied to any system that does not have specific credentials. 
host = 
* The host for the default stanza must be specified and left blank as shown above.

username = <username>
* The username setting specifies in plain text the username applied to any system that does not have specific credentials.

password = <password>
* The password setting specifies the password applied along with the username above to any system that does not have specific credentials. 
* The password setting is encrypted in this file and should have a post-encryption format similar to: {RC4}Np2ivtHJkdU
* Setting of passwords/encrypting them is done via the credentials.pl script. See its documentation for further details.


[<specific credentials spec>]
* There should be one of these stanzas per set of specific credentials, each with a unique name
host = <host selector> 
* The host setting determines which systems (ESX/i hosts or Virtual Centers) the set of specific credentials should be applied to.
* A "Single Server" stanza would employ a the hostname (e.g. esxi123.mycompany.com)  as the host setting. This CANNOT be modified 
  without re-encrypting the file.
* A "List"stanza would employ a pipe (|) delimited list of hostnames with a trailing pipe (e.g. esxi123.mycompany.com|vc123.mycompany.com|)
  as the host setting. Any system with a hostname in this list would have the associated specific credentials applied to it. Systems 
  may be appended or removed from the list without re-encrypting the file. 
* A "Regex" stanza would employ a perl compatible regular expression with a leading and trailing forward slash character 
  (e.g. /^esx.*\.mycompany\.com$/) as the host setting. Any system whose hostname was a regex match to the regular expression
  would have the associated specific credentials applied to it. This CANNOT be modified without re-encrypting the file.

username = <username>
* The username setting specifies in plain text the username for this set of specific credentials.

password = <password>
* The password setting specifies the password applied along with the username above for this set of specific credentials
* The password setting is encrypted in this file and should have a post-encryption format similar to: {RC4}Np2ivtHJkdU
* Setting of passwords/encrypting them is done via the credentials.pl script. See its documentation for further details.