rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jasha Joachimsthal (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RAVE-136) Define account administrator role.
Date Wed, 05 Oct 2011 13:46:34 GMT

     [ https://issues.apache.org/jira/browse/RAVE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jasha Joachimsthal resolved RAVE-136.

    Resolution: Fixed
      Assignee: Marlon Pierce  (was: Jasha Joachimsthal)

In the inital data there are 2 authorities now: "ROLE_USER" and "ROLE_ADMIN".
Canonical has the ROLE_ADMIN, the other users ROLE_USER.
In the Spring security configuration the /app/admin/** is only accessible for ROLE_ADMIN (no
request mapping yet), other portal pages are accessible for both ROLE_USER and ROLE_ADMIN.
> Define account administrator role. 
> -----------------------------------
>                 Key: RAVE-136
>                 URL: https://issues.apache.org/jira/browse/RAVE-136
>             Project: Rave
>          Issue Type: Sub-task
>          Components: rave-core
>            Reporter: Marlon Pierce
>            Assignee: Marlon Pierce
>             Fix For: 0.5-INCUBATING
> Users with account administrator roles will be able to approve, enable, disable, and
lock user accounts, implementing some additional fields in User.java.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message