Changes between Version 3 and Version 4 of RepAaa

Timestamp:

Oct 5, 2010, 3:16:43 PM (14 years ago)

Author:

tim.bauge

Comment:

--

RepAaa

@@ -54 +54 @@
 ==== Registering the policy ====
 There may be multiple AAA services running in the domain, and the resource provider must choose which to use (in a real life deployment they may differ in terms of SLAs, or service cost etc).
-
-The AAA service implementation is provided as a WAR file deployed in a servelet container (see [wiki:Aaa|here]), and the policy files should be placed in the "WEB-INF/classes/authorisation-policies" folder of the WAR file, and the AAA service restarted.
-
+The AAA service implementation is provided as a WAR file deployed in a servelet container (see [wiki:Aaa|here]), and the policy files should be placed in the "/WEB-INF/classes/authorisation-policies" folder of the WAR file, and the AAA service restarted.
 Adding, modifying or removing policies is done by changing the content of the "WEB-INF/classes/authorisation-policies" folder.
-==== Enforcing the AAA decision ====
-The REP must request an access control decision from the AAA service each time a client tries to access a service. To do this, the REP must know the URL of the 
-
 ==== Configuring the Access Controlled REP ====
-The REP may be configured in the messages.properties file located in /WEB-INF/classes. 
+The access controlled REP is provided as a WAR file, to be deployed in a servelet container such as Apache Tomcat. The REP must be configured in the messages.properties file located in /WEB-INF/classes directory of the WAR file.
 ||= Property =||= Description =||
 ||rep.id||The identifier of the REP, which should be the URI||