You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rave.apache.org by "Scott Wilson (Commented) (JIRA)" <ji...@apache.org> on 2012/03/01 14:05:59 UTC

[jira] [Commented] (RAVE-495) Unable to login to Wookie as admin user when currently deployed with rave.

    [ https://issues.apache.org/jira/browse/RAVE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220012#comment-13220012 ] 

Scott Wilson commented on RAVE-495:
-----------------------------------

As an alternative, what about if Wookie allowed the top-level Tomcat "admin" as well as "widgetadmin" roles to perform Wookie admin tasks?
                
> Unable to login to Wookie as admin user when currently deployed with rave.
> --------------------------------------------------------------------------
>
>                 Key: RAVE-495
>                 URL: https://issues.apache.org/jira/browse/RAVE-495
>             Project: Rave
>          Issue Type: Improvement
>          Components: build & development
>    Affects Versions: 0.9-INCUBATING
>         Environment: n/a
>            Reporter: Paul Sharples
>            Priority: Minor
>
> Normally when wookie is deployed under tomcat, you would have to update your copy of '/tomcat*/conf/tomcat-users.xml' to include a 'widgetadmin' role. This allows you to login to wookie as the admin user and be able to do things such as import new widgets and set policies, etc.
> To fix this, we could update/replace that file as part of the build process.

--
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