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

Secured pages should redirect to login prompt instead of generating 404

XMLWordPrintable

      Using version 1.475

      We have set our permissions to disallow anonymous "read job". What ends up happening is that when you are logged out and try to access a build or a job (Example: http://jenkins.core:8080/job/campaign-management%20release-candidate/210/) Jenkins returns 404 instead of redirecting you to the log-in page. At the minimum, it should display an error message that you are not authenticated.

      Error returned below:

      Status Code: 404

      Exception:
      Stacktrace:
      (none)

      Generated by Winstone Servlet Engine v0.9.10 at Wed Aug 08 16:00:55 EDT 2012

          [JENKINS-14736] Secured pages should redirect to login prompt instead of generating 404

          evernat added a comment -

          reproduced using Jenkins 1.526

          evernat added a comment - reproduced using Jenkins 1.526

          mdp added a comment -

          Isn't it what the discover permission is for?

          mdp added a comment - Isn't it what the discover permission is for?

          Klokie Grossfeld added a comment - - edited

          You're right - I had no idea! I enabled the "Discover" permission for Jobs, and now anonymous users are redirected to the login form.
          I've noted this in the documentation for Matrix-based security.
          Cheers!

          Klokie Grossfeld added a comment - - edited You're right - I had no idea! I enabled the "Discover" permission for Jobs, and now anonymous users are redirected to the login form. I've noted this in the documentation for Matrix-based security . Cheers!

          Joshua Ayson added a comment -

          When using discover permission with anonymous user it overrides ability to limit build access to users assigned explicit permissions set by turning authenticated to just overall read, without build or view read. In this case with discover on, authenticated users see no jobs.

          Joshua Ayson added a comment - When using discover permission with anonymous user it overrides ability to limit build access to users assigned explicit permissions set by turning authenticated to just overall read, without build or view read. In this case with discover on, authenticated users see no jobs.

            Unassigned Unassigned
            arov Alex Rovner
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: