You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by Apache Wiki <wi...@apache.org> on 2006/11/27 16:11:53 UTC

[Jackrabbit Wiki] Trivial Update of "JackrabbitOnJbossSecurity" by DarrenHartford

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by DarrenHartford:
http://wiki.apache.org/jackrabbit/JackrabbitOnJbossSecurity

------------------------------------------------------------------------------
    *  repository.xml
  
  ----
- == Configuring Security Domain ==
+ == Configuring Security Authentication Policy ==
- The security domain will tie jackrabbit and the jboss security systems together.  The default security domain is called '''Jackrabbit''', but can be changed if necessary (especially if you already have an existing domain configured in jboss login-config.xml that you would like to re-use).
+ The security authentication policy will tie jackrabbit and the jboss security systems together.  The default security policy is called '''Jackrabbit''', but can be changed if necessary (especially if you already have an existing domain configured in jboss login-config.xml that you would like to re-use).
+ 
+ The security policy is repository-wide, regardless of workspace(s). If you need different security/authentication, you will need different repositories (i.e. new repository.xml for each repository).  However, if you can use the same authentication but have different authorization requirements, you can use the same repository with a custom AccessManager.
  
  
  '''repository.xml'''
@@ -56, +58 @@

  TODO
  ----
  == JBoss Mbean Dynamic Login Config option ==
- This is for deployment of the authentication login modules outside of the login-config.xml.  The reasoning is usually policy-oriented and/or preference.  This is a jboss-specific option not related to Jackrabbit -- all jackrabbit configuration related to login-config.xml will now go into the jackrabbit-login-config.xml below.
+ This is for deployment of the authentication login modules outside of the login-config.xml.  The reasoning is usually company-policy-oriented and/or preference.  This is a jboss-specific option not related to Jackrabbit -- all jackrabbit configuration related to login-config.xml will now go into the jackrabbit-login-config.xml below.
  
   * Create a $JBOSS_HOME/server/<default>/deploy/jackrabbitsecurity.rar directory (yes, name the directory with .rar at the end).