Changes between Version 7 and Version 8 of FeddSkelPlugin

Timestamp:

Jun 27, 2010 11:12:53 AM (14 years ago)

Author:

faber

Comment:

--

FeddSkelPlugin

@@ -14 +14 @@
  * Copy [attachment:skel_access] into the configuration directory
  * [FeddConfig#MakingaFedidCertificate Create a certificate representing a fedid] in this directory.
+ * Copy [attachment:guest.pem] to your local machine.  It need not be in the configuration directory.
  * Follow the steps below to edit [attachment:skel.conf] for your installation.
 
@@ -73 +74 @@
 The two or three parameters in this section control overall operation of the plug-in, specifically what prinicpal ID (that is which [FeddAbout#GlobalIdentifiers:Fedids fedid]) it uses and what TCP port it provides services on.  '''cert_file''' and '''cert_pwd''' select the X.509 certificate and encyrption password, if any, used to identify the plug-in.  The '''services''' parameter controls which ports and transports are used.  The sample file serves SOAP traffic on port 13230. [FeddConfig#GlobalOptions Other choices] are possible.
 
+== The Access Database ==
+
+The [attachment:skel_access access database] has only one entry in it, which allows access from a user '''guest''' in the '''testing''' project project when asserted by [FeddAbout#GlobalIdentifiers:Fedids fedid] b55205ac843c40ce9c9feb3b358bff782ed337fd.  That fedid is the one asserted by the fedd experiment controller running at DETER.
+
+For testing plug-ins the DETER experiment controller will permit anyone connecting with the fedid encoded in the [attachment:guest.pem guest.pem] file to request operations with that three-level name.  Once your plug-in does something interesting, you should reduce or eliminate the access rights of that user.
+
+The rest of the line gives that user access permissions and the local permission state '''Local_attr'''.  This is more to show how to assign such allocations, which will be meaningful in real installations.  For example, see the configurations of other plug-ins.