Creating a new credential with an existing ID returns a 302 response code instead of blocking the submission

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: credentials-plugin
    • None
    • Environment:
      Jenkins 2.389

      When attempting to add a new credential in Jenkins with an already existing ID, the user is notified that "This ID is already in use", however, the user is able to click on the 'create' button which results in a 302 status code. The expected behavior should be to block the submission in case of an already-used ID or return an error status.

            Assignee:
            Unassigned
            Reporter:
            Beni Peled
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: