Rave
  1. Rave
  2. RAVE-495

Unable to login to Wookie as admin user when currently deployed with rave.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.9-INCUBATING
    • Fix Version/s: 0.10.1
    • Component/s: build & development
    • Labels:
      None
    • Environment:
      n/a

      Description

      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.

        Activity

        Hide
        Scott Wilson added a comment -

        As an alternative, what about if Wookie allowed the top-level Tomcat "admin" as well as "widgetadmin" roles to perform Wookie admin tasks?

        Show
        Scott Wilson added a comment - As an alternative, what about if Wookie allowed the top-level Tomcat "admin" as well as "widgetadmin" roles to perform Wookie admin tasks?
        Hide
        Paul Sharples added a comment -

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

        Show
        Paul Sharples added a comment - 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/ )
        Hide
        Matt Franklin added a comment -

        Is there a way to pull the admin users from the database so that Wookie doesn't need to have separate configuration in tomcat?

        Show
        Matt Franklin added a comment - Is there a way to pull the admin users from the database so that Wookie doesn't need to have separate configuration in tomcat?
        Hide
        Paul Sharples added a comment -

        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

        Show
        Paul Sharples added a comment - 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
        Hide
        Jasha Joachimsthal added a comment -

        Thanks for the patch

        Show
        Jasha Joachimsthal added a comment - Thanks for the patch

          People

          • Assignee:
            Jasha Joachimsthal
            Reporter:
            Paul Sharples
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development