Changes between Version 13 and Version 14 of Aaa


Ignore:
Timestamp:
Oct 12, 2010, 4:47:09 PM (14 years ago)
Author:
tim.bauge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Aaa

    v13 v14  
    3131||key.alias||Key alias, defined during the keystore deployement||
    3232||key.password||Key password, defined during the keystore deployement||
    33 ||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/)||
    34 ||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/)||
    35 ||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/)||
    36 ^^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.
     33||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/)||
     34||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/)||
     35||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/)||
     36^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.
    3737* sts.war/WEB-INF/classes/trustedEntities/hostedStsMetadata.xml
    3838Configuration fields:
    … …  
    111111
    112112=== Management ===
     113==== Policy management ====
     114
    113115==== Accounting interface ====
    114116The Accounting data can be viewed at <aaaservice URI>/REST/Accounting