Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42354

ATH must support users and run logged in where needed

XMLWordPrintable

    • 1.0

      The ATH runs with security turned off right now for historical reasons.

      This is not a recommended configuration and prevents it from testing things like:

      • Personalization
      • Creation
      • Permissions
        The ATH should be able to run tests as a logged in user (or different users with different permissions).

      cc imeredith

          [JENKINS-42354] ATH must support users and run logged in where needed

          Cliff Meyers added a comment -

          I had previously suggested that perhaps we could use a custom subclass of LocalController to set up a Jenkins home with the appropriate configuration. However imeredith made what might be a better suggestion which is that this could be set up via a plugin that's bundled with the Jenkins deployed by ATH. I'm not knowledgeable enough to enumerate the pros and cons though.

          Cliff Meyers added a comment - I had previously suggested that perhaps we could use a custom subclass of LocalController to set up a Jenkins home with the appropriate configuration. However imeredith made what might be a better suggestion which is that this could be set up via a plugin that's bundled with the Jenkins deployed by ATH. I'm not knowledgeable enough to enumerate the pros and cons though.

          Michael Neale added a comment -

          This isn't needed for 1.0 but Ivan is taking a look as it can drop any time, it only improves coverage. 

          Michael Neale added a comment - This isn't needed for 1.0 but Ivan is taking a look as it can drop any time, it only improves coverage. 

            imeredith Ivan Meredith
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: