This routine will configure this machine for use with Policy
Director.
To illustrate how this configuration might be done, imagine the following set of
admin commands had been run on the ivmgrd server (assume it's timon.i.com):
pdadmin -a sec_master -p xxxpassword
user create PdPermission9993 cn=PdPermission/gordo,o=myCompany PdPermission/gordo PdPermission somePW9993
user modify PdPermission9993 account-valid yes
group modify remote-acl-users add PdPermission9993
(This example assumes that the LDAP root for the users is anchored at o=myCompany, and
uses the convention that the "distinguishing" part of the distinguished name will in fact
be the hostname of the machine, which in this example is "gordo".)
The command that could be issued now on gordo is:
java com.tivoli.mts.SvrSslCfg cn=PdPermission/gordo,o=myCompany xxxpassword timon.i.com rafiki.i.com
(which is taking the default SSL port numbers for ivacld and ivmgrd, and configuring gordo
to use the ivacld on rafiki.i.com).
- Parameters:
dn
- The distinguished name of the principal that this machine is to use.pw
- The password for sec_master.ivmgrd-hostname
- The name of the machine that is running ivmgrd.ivacld-hostname
- The name of the machine that is running the instance of ivacld
that this machine is to communicate with.ivmgrd-port
- The SSL port number for ivmgrd, if other than the default (7135).ivacld-port
- The SSL port number for ivacld, if other than the default (7136).- Throws:
java.lang.IllegalArgumentException
- if it seems like bad data was passed in.java.lang.IllegalStateException
- if this request could not be processed.