Jörn Nettingsmeier wrote:
Andreas Hartmann wrote:
Joern Nettingsmeier wrote:
Andreas Hartmann wrote:
Doug Chestnut wrote:
Hi Joern,
The first thing to change would be to add
<usecase id="admin.changePassword">
<role id="admin"/>
</usecase>
to your (and our default pubs) pubs usecase-policies.xml
Exactly - and we could declare two different usecases so that one can
be permitted only for admins and the other one (with entering the old
password) for all users (see my other reply).
yes, that sounds nice. i'll try to get my head around it tonight...
Jörn, did you already find a solution?
I thought about it too yesterday night and made some minimal changes,
but I wanted to wait for your ideas before checking them in.
Should I go ahead, or are you also working on this issue?
i'm still at it. the thing i'm stuck with atm is that i don't understand
the mapping from usecase names in usecases-policy.xml to the actual
usecases. in the file, there are no prefixes, and in real life, almost
all usecases are prefixed "site.usecaseName" or "admin.usecaseName".
?
and somebody seems to have anticipated the problem and stopped halfway
through: there are policies for userChangePasswordUser and
userChangePasswordAdmin, but i think there's no actual code for those
usecases...
if you want to commit your changes, that's fine, i'm still in the
process of understanding how usecase policies are done.
OK, I added a new class UsecasePasswordWithCheck to avoid that the
password check option is set by a parameter. The code became also a
bit cleaner this way.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
