Update of /var/cvs/applications/cloudcontext/documentation
In directory james.mmbase.org:/tmp/cvs-serv2951
Modified Files:
cloudcontextsecurity.xml
Log Message:
added some documentation on how you could use a different users builder
See also: http://cvs.mmbase.org/viewcvs/applications/cloudcontext/documentation
Index: cloudcontextsecurity.xml
===================================================================
RCS file:
/var/cvs/applications/cloudcontext/documentation/cloudcontextsecurity.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- cloudcontextsecurity.xml 25 Feb 2004 09:11:36 -0000 1.5
+++ cloudcontextsecurity.xml 15 Dec 2008 15:22:50 -0000 1.6
@@ -5,7 +5,7 @@
<articleinfo>
<title>Cloud Context Security</title>
<date>2003-09-12</date>
- <edition>$Id: cloudcontextsecurity.xml,v 1.5 2004/02/25 09:11:36 michiel
Exp $</edition>
+ <edition>$Id: cloudcontextsecurity.xml,v 1.6 2008/12/15 15:22:50 michiel
Exp $</edition>
<authorgroup>
<author>
<firstname>Michiel</firstname>
@@ -47,7 +47,7 @@
edited.
</para>
</section>
- <section id="object model">
+ <section id="object_model">
<title>Object model</title>
<para>
Because of the nature of this security implementation, the object model
of your MMBase
@@ -236,6 +236,50 @@
</varlistentry>
</variablelist>
</para>
+ <section id="otherbuilders">
+ <title>Using different builders</title>
+ <para>
+ Cloud context security provides the builder mmbaseuser, mmbasegroups,
and mmbasecontexts to
+ store authentication and authorization information in. In some cases,
e.g. when trying to
+ deploy cloud context security on an environment which used to have a
different security
+ implementation, it may be desired to use other builders to store users
and context in.
+ </para>
+ <section id="other_users">
+ <title>Using another builder to store users in</title>
+ <para>If you want to store the user in a different builder, then you
have to do the
+ following</para>
+ <orderedlist>
+ <listitem>
+ <para>Choose your builder</para>
+ </listitem>
+ <listitem>
+ <para>You can define a 'security_editor_fields' property in this
builder, to defined
+ which fields must be edited in the the security editors.</para>
+ </listitem>
+ <listitem>
+ <para>Extend
+
<classname>org.mmbase.security.implementation.cloudcontext.Authenticate</classname>
and
+ override the method getUserProvider. Implement your own
<classname>Provider</classname>, it can e.g. be the
+ class of your own users builder, and implement in your
+ <classname>Authenticate</classname> how it should be obtained. The
method
+ <function>getUserBuilder</function> should return the builder
(<constant>this</constant>
+ in case the <classname>Provider</classname>
<emphasis>is</emphasis> the builder).
+ </para>
+ </listitem>
+ <listitem>
+ <para>Make sure the relations <your builder> to mmbaseranks
with role 'rank',
+ from mmbasegroups to <your builder> with role 'contains' and
mmbasecontext to
+ <your builder > with role 'grants' are possible.
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="other_context">
+ <title>Using another builder to store possible contexts</title>
+ <para>
+ </para>
+ </section>
+ </section>
</section>
<section id="conversion">
<title>Conversion from `XML' context security</title>
_______________________________________________
Cvs mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/cvs
