You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Michael Shoener <ms...@softwareapps.net> on 2009/09/25 19:57:26 UTC
What is the security workspace for?
What exactly is the "security" workspace used for?
I tried deleting it but it always recreates it when I restart my app server.
Is it needed and if not how do I stop it from recreating it.
Best Regards,
Michael Shoener
Support Staff
Software Application Services, Inc.
RE: What is the security workspace for?
Posted by Michael Shoener <ms...@softwareapps.net>.
Thanks, that did the trick.
Best Regards,
Michael Shoener
Support Staff
Software Application Services, Inc.
-----Original Message-----
From: Angela Schreiber [mailto:anchela@day.com]
Sent: Friday, September 25, 2009 2:19 PM
To: users@jackrabbit.apache.org
Subject: Re: What is the security workspace for?
Michael Shoener wrote:
> What exactly is the "security" workspace used for?
the initial intention of the issue JCR-1171 (Contribute Pluggable Permission
and User Management to Jackrabbit) was to have the ability to store users
and groups in a separate workspace and making them available to other
workspaces through the UserManager.
you can turn this (separate wsp) of by changing the repository's
security-manager configuration (there is a param called "workspaceName" if
i'm not mistaken).
and if i remember properly the default workspace is used if the param is
missing.
that's the work-in-progress status in 1.5 and 1.6... not sure yet, how this
will exactly be for 2.0.
hope that helps
angela
Re: What is the security workspace for?
Posted by Angela Schreiber <an...@day.com>.
Michael Shoener wrote:
> What exactly is the "security" workspace used for?
the initial intention of the issue JCR-1171
(Contribute Pluggable Permission and User Management to Jackrabbit)
was to have the ability to store users and groups
in a separate workspace and making them available to
other workspaces through the UserManager.
you can turn this (separate wsp) of by changing the
repository's security-manager configuration (there is a param called
"workspaceName" if i'm not mistaken).
and if i remember properly the default workspace is used if
the param is missing.
that's the work-in-progress status in 1.5 and 1.6... not sure
yet, how this will exactly be for 2.0.
hope that helps
angela