Andreas Hartmann wrote:
Jörn Nettingsmeier wrote:
Doug Chestnut wrote:
Andreas Hartmann wrote:
Jörn Nettingsmeier wrote:
hi *!
while i'm preparing a patch to change usecase policies to
deny-by-default, it occured to me that we need to modularize
default usecase policies...
how hard will it be to implement the following:
* every module that contains usecases must also contain a
config/ac/usecase-policies.xml
-1
I have to agree here -1 on usecases setting their own policies.
in principle, i wholeheartedly agree. but how do we make the stuff
usable? we can't expect users to walk through all modules, grep for
usecase names and guess the appropriate permissions.
To simplify this, I added an XSLT which extracts all available
usecases from cocoon.xconf and initializes the policies with the
admin role.
lenya/trunk/src/modules-core/usecase-impl/xslt/initUsecasePolicies.xsl
It's not perfect, but it might help to get started.
BTW, tt shouldn't be too hard to build a GUI for that.
neat idea, thanks!
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
