Links to restricted jobs fail with 404 instead of prompting the user for credentials

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      This is more of a usability improvement. When a user clicks a link to a job that is restricted by security they get a 404 error and a blank stack trace. It would be better if instead of this they see a log-in screen. This conveys the message that they don't have access rather than something bad just happened with Jenkins.

            Assignee:
            Unassigned
            Reporter:
            Jake Coffman
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: