Changes between Version 7 and Version 8 of RepAaa

Timestamp:

Oct 13, 2010, 9:53:26 AM (14 years ago)

Author:

tim.bauge

Comment:

--

RepAaa

@@ -8 +8 @@
 [[PageOutline(2-3,Table of Contents,inline)]]
 
-== How-to: adding access control to my REP ==
-=== Choosing the form of access control ===
+== Choosing the form of access control ==
 Access control in SENSEI can be done on the basis of the user's privileges, or on the basis of payment. This choice is made by the resource provider. If the access control should be performed based on payment, the REP should be registered with a payment based AAA service. Instructions for this can be found [[wiki:PrivacyAndBilling|here]].
 If the access control should be performed based on privileges, the REP should be registered with a privilege based AAA service. Instructions for this can be found below.
-=== Defining an access policy ===
+
+== Deployment of a AAA enabled REP ==
+A deployable AAA enabled REP is provided for testing purposes. This REP is designed to exercise the AAA functions, but does not implement plug and play capability for resources. The REP comes with an integrated synthetic sensor producing random values, as a proof of concept rather than an operational component. AAA functionality should be added to operational REPs, based on the specification provided [here]. This is a developer concern, and is therefore not described further here.
+=== Getting the software components ===
+* Apache Tomcat servlet container or equivalent
+Instructions for setting up Apache Tomcat can be found [http://tomcat.apache.org/tomcat-6.0-doc/setup.html here].
+* STS WAR file
+The STS WAR file can be downloaded from here: [wiki:trt-war AAA downloads page].
+The WAR files should be first configured for the deployment setup (see below) and then deployed in the servlet container. For Tomcat, instructions are provided [http://tomcat.apache.org/tomcat-6.0-doc/deployer-howto.html here] (see in particular the "Deployment on Tomcat startup" section).
+=== Configuration ===
+The WAR file contains one file which need configuring to run correctly on the target deployment platform. Each field requiring a deployment specific value has been identified with the string "REPLACE:". Other fields have been set to typical defaults which should satisfy most deployments. These can however be modified for advanced tuning of the AAA service. For more information contact TRT (UK).
+The WAR file is an archive containing object code, presentation templates and configuration files. The downloaded WAR file should therefore be opened (e.g. using [http://www.7-zip.org/ 7-zip]) to edit the following configuration file:
+* rep.war/WEB-INF/classes/messages.properties
+||= '''Field''' =||= '''Expected content''' =||
+||rep.id||The identifier of the REP, which should be the URL of this REP||
+||aaaservice.uri||The URL of the AAA Service which will provide access control decisions||
+||resDir.uri||The URL of the SENSEI resource directory||
+
+== Setting access policies ==
+=== Writing policies ===
 First a set of policies must be defined to specify the access rules which should apply. These are specified in a text file with the .drl extension.
 For the enthusiasts, a full description of the rules language can be found [[http://downloads.jboss.com/drools/docs/5.1.1.34858.FINAL/drools-expert/html/ch04.html|here]]. We would recommend keeping things simple, and therefore provide an example below.
@@ -53 +71 @@
 
 The roles which are evaluated in these rules are the roles contained in the tokens issued by the [wiki:Aaa STS].
-=== Registering the policy ===
+=== Registering policies ===
 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.
 Adding, modifying or removing policies is done by changing the content of the aaa.war/WEB-INF/classes/authorisation-policies folder.
-=== Configuring the Access Controlled REP ===
-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||
-||aaaservice.uri||The URI of the AAA Service||
-||aaaservice.request.uri||The URI of the Request interface of the AAA Service||
-||resDir.uri||The URI of the resource directory||