You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Paul Sharples (Created) (JIRA)" <ji...@apache.org> on 2012/03/01 13:53:59 UTC
[jira] [Created] (RAVE-495) Unable to login to Wookie as admin user
when currently deployed with rave.
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
[jira] [Commented] (RAVE-495) Unable to login to Wookie as admin
user when currently deployed with rave.
Posted by "Scott Wilson (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (RAVE-495) Unable to login to Wookie as admin
user when currently deployed with rave.
Posted by "Matt Franklin (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220126#comment-13220126 ]
Matt Franklin commented on RAVE-495:
------------------------------------
Is there a way to pull the admin users from the database so that Wookie doesn't need to have separate configuration in tomcat?
> 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
[jira] [Commented] (RAVE-495) Unable to login to Wookie as admin
user when currently deployed with rave.
Posted by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220129#comment-13220129 ]
Paul Sharples commented on RAVE-495:
------------------------------------
Well there is only one admin account, which we currently define in tomcat-users.xml using roles. This is then referenced from the web.xml for certain resources
> 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
[jira] [Commented] (RAVE-495) Unable to login to Wookie as admin
user when currently deployed with rave.
Posted by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220021#comment-13220021 ]
Paul Sharples commented on RAVE-495:
------------------------------------
Okay seems sensible. My only slight concern is that is the top level "admin" account may be not alway be enabled by default and so we may have to update the users file anyway (after a quick google on the subject). Anyway, I've created a patch which would address the original problem (https://reviews.apache.org/r/4126/)
> 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
[jira] [Resolved] (RAVE-495) Unable to login to Wookie as admin
user when currently deployed with rave.
Posted by "Jasha Joachimsthal (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jasha Joachimsthal resolved RAVE-495.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.10-INCUBATING
Assignee: Jasha Joachimsthal
Thanks for the patch
> 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
> Assignee: Jasha Joachimsthal
> Priority: Minor
> Fix For: 0.10-INCUBATING
>
>
> 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