Changes between Version 14 and Version 15 of Aaa

Timestamp:

Oct 12, 2010, 4:53:29 PM (14 years ago)

Author:

tim.bauge

Comment:

--

Aaa

@@ -31 +31 @@
 ||key.alias||Key alias, defined during the keystore deployement||
 ||key.password||Key password, defined during the keystore deployement||
-||partner.aaaservice.filepath ^1||File path of AAA Service metadata. This metadata file is available from the AAA service provider (file name hostedAaaMetadata.xml found in aaa.war/WEB-INF/classes/trustedEntities/)||
-||partner.sts1.filepath ^1||File path of a trusted STS metadata if needed (one with which a federation agreement is in place). This metadata file is available from the remote STS provider (file name hostedStsMetadata.xml found in sts.war/WEB-INF/classes/trustedEntities/)||
-||partner.sts2.filepath ^1||File path of another trusted STS metadata if needed (one with which a federation agreement is in place). This metadata file is available from the remote STS provider (file name hostedStsMetadata.xml found in sts.war/WEB-INF/classes/trustedEntities/)||
-^1 For simplicity of configuration, the STS is by default set to have one AAA service which it trusts, and up to two federated STS (i.e. a federation of three in all). If more AAA services of STSs are required to be used in the deployment, further configuration changes are required which are beyond the scope of this cookbook. Please contact TRT (UK) directly for further instructions. 
+||partner.aaaservice.filepath^*||File path of AAA Service metadata. This metadata file is available from the AAA service provider (file name hostedAaaMetadata.xml found in aaa.war/WEB-INF/classes/trustedEntities/)||
+||partner.sts1.filepath^*||File path of a trusted STS metadata if needed (one with which a federation agreement is in place). This metadata file is available from the remote STS provider (file name hostedStsMetadata.xml found in sts.war/WEB-INF/classes/trustedEntities/)||
+||partner.sts2.filepath^*||File path of another trusted STS metadata if needed (one with which a federation agreement is in place). This metadata file is available from the remote STS provider (file name hostedStsMetadata.xml found in sts.war/WEB-INF/classes/trustedEntities/)||
+^*
+For simplicity of configuration, the STS is by default set to have one AAA service which it trusts, and up to two federated STS (i.e. a federation of three in all). If more AAA services of STSs are required to be used in the deployment, further configuration changes are required which are beyond the scope of this cookbook. Please contact TRT (UK) directly for further instructions. 
 * sts.war/WEB-INF/classes/trustedEntities/hostedStsMetadata.xml
 Configuration fields:
@@ -112 +113 @@
 === Management ===
 ==== Policy management ====
-
+REP access policies must be uploaded to the AAA service. Policy files must be placed in aaa.war/WEB-INF/classes/authorisation-policies, and the AAA service restarted after modification.
+See [wiki:RepAaa here] for more information on policies.
 ==== Accounting interface ====
 The Accounting data can be viewed at <aaaservice URI>/REST/Accounting