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

Misleading message "Consumer key cannot be empty"

    • Bitbucket Server Integration 3.3.2

      To reproduce:

      1. Navigate to "Dashboard" - "Manage Jenkins" - "Security" - "Manage Bitbucket Server consumers" - "Register new consumer".
      2. Click the "Consumer key" field and type "bitbucket.example".
      3. Then click the "Shared secret" field.

      Expected behavior:

      Either the form accepts "bitbucket.example" as the consumer key, or rejects it with a clear message such as "The consumer key must consist of alphanumeric characters and hyphens only".

      Actual behavior:

      The form displays "Consumer key cannot be empty", even though the consumer key is not empty.

          [JENKINS-69288] Misleading message "Consumer key cannot be empty"

          Thanks for the report Kalle- I think this wasn't updated when we last changed the consumer form. This will go out with our next release.

          Martin Henschke added a comment - Thanks for the report Kalle- I think this wasn't updated when we last changed the consumer form. This will go out with our next release.

          This was fixed in https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/358, reverted in https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/360, unreverted in https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/365, and finally released in Bitbucket Server Integration version 3.3.2 on 2022-10-24.

          I'm not changing the state of this issue yet, because I don't know whether the fix has been tested.

          Kalle Niemitalo added a comment - This was fixed in https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/358 , reverted in https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/360 , unreverted in https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin/pull/365 , and finally released in Bitbucket Server Integration version 3.3.2 on 2022-10-24. I'm not changing the state of this issue yet, because I don't know whether the fix has been tested.

          Dyon added a comment - - edited

          Fix has been verified to work. Test for the fix can be found in 

          OAuthEntryTest#testDoCheckConsumerKeyWithIllegalCharacters  

          Dyon added a comment - - edited Fix has been verified to work. Test for the fix can be found in  OAuthEntryTest#testDoCheckConsumerKeyWithIllegalCharacters

            Unassigned Unassigned
            kon Kalle Niemitalo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: