Created the ATS daemon and made necessary RPM install changes to allow
for its deployment.
This commit is contained in:
@@ -99,7 +99,7 @@ The following is an example svc.settings file:
|
||||
<IAConfigFile>/home/jluciani/jakarta-tomcat-5.0.28/webapps/CasaAuthTokenSvc/WEB-INF/conf/iaRealms.xml</IAConfigFile>
|
||||
<ReconfigureInterval>60</ReconfigureInterval>
|
||||
<startSearchContext>o=novell</startSearchContext>
|
||||
<KeyStoreUser>privKey<KeyStoreUser>
|
||||
<SigningKeyAliasName>signingKey<SigningKeyAliasName>
|
||||
<KeyStorePwd>foobar<KeyStorePwd>
|
||||
</settings>
|
||||
|
||||
@@ -135,18 +135,20 @@ Note the following about the sample svc.settings file:
|
||||
to the identity abstraction configuration file where it belongs. Once this is done,
|
||||
the setting will no longer be recognized within the svc.settings file.
|
||||
|
||||
- The KeyStoreUses setting specifies the user's alias name in the keystore that identifies
|
||||
the private key that is to be used to sign tokens.
|
||||
- The SigningKeyAliasName setting specifies the alias name of the entry in the keystore
|
||||
with the private key utilized to sign tokens. The value of this setting defaults to
|
||||
"signingKey".
|
||||
|
||||
- The KeyStorePwd setting specifies the password of the user specified by KeyStoreUser to get
|
||||
the private signing key from the keystore.
|
||||
- The SigningKeyPassword setting specifies the password utilized to protect the private key
|
||||
used for signing tokens that is stored in the keystore. The value of this setting defaults to
|
||||
"secret".
|
||||
|
||||
ATSs digitally sign tokens, for this purpose it is necessary that keys be generated and installed
|
||||
in a keystore whose location and properties are configured in the crypto.properties file present in
|
||||
the "classes" folder under the WEB-INF folder of the AuthTokenSvc application
|
||||
($CATALINA_HOME/webapps/CasaAuthTokenSvc/WEB-INF/classes). Please note that you must edit the
|
||||
crypto.properties file with the appropriate information once the AuthTokenSvc is deployed to
|
||||
a Tomcat server.
|
||||
a Tomcat server to deal with your configuration requirements.
|
||||
|
||||
CONFIGURING SERVICES TO CONSUME CASA AUTHENTICATION TOKENS
|
||||
|
||||
|
||||
Reference in New Issue
Block a user