Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-17077

Umlaut characters in JIRA User Full Name breaks build trigger from JIRA

    XMLWordPrintable

Details

    • Bug
    • Resolution: Tracked Elsewhere
    • Medium
    • None
    • 5.9.7
    • None

    Description

      Summary

      When using Release and Build intergration feature from JIRA, umlaut characters are not encoded properly and breaks the OAuth signature

      Steps to Reproduce

      1. Setup Application Links between JIRA and Bamboo
      2. Create a user with umlaut characters in the full name. Example: Länge
      3. Trigger a build by Release and Build a version from JIRA

      Expected Results

      The build plan triggered properly.

      Actual Results

      The below exception is thrown in the atlassian-bamboo.log file:

      2016-01-04 17:32:30,069 WARN [http-bio-8085-exec-6] [AuthenticatorImpl] Problem encountered authenticating OAuth client for url "http://localhost:8085/bamboo/rest/api/latest/queue/TP-BP.json", error was "signature_invalid", with parameters "{oauth_problem=signature_invalid, oauth_signature=EMrhELQ12QEVj+B7YqI3wWKQR0eZ7Ud+hTC2sSb8JIBmG17paSJG5C/zvriPOM08nSegYFV0Llj3MvSO6OwhN9ufrTeJzXmb3Iyr8yvOPgajGt3fo1Pqy9OalJoK0+hSRyn2bmisCUa33T7zX2RfIbzaqnm25cOGWBsbGQmLHtk=, oauth_signature_base_string=POST&http%3A%2F%2Flocalhost%3A8085%2Fbamboo%2Frest%2Fapi%2Flatest%2Fqueue%2FTP-BP.json&bamboo.customPlanTriggerKey%3Dcom.atlassian.bamboo.plugin.jira%253AjiraReleasePlanTrigger%26bamboo.customTriggerReasonKey%3Dcom.atlassian.bamboo.plugin.jira%253AjiraReleaseTriggerReason%26bamboo.triggerReason.jiraBaseUrl%3Dhttp%253A%252F%252Flocalhost%253A8080%252Fjira%26bamboo.triggerReason.jiraProjectKey%3DPRA%26bamboo.triggerReason.jiraProjectName%3DPROJECT%2520A%26bamboo.triggerReason.jiraUserDisplayName%3DL%25EF%25BF%25BDnge%26bamboo.triggerReason.jiraUsername%3Dadmin%26bamboo.triggerReason.jiraVersion%3D4.1%26bamboo.triggerReason.jiraVersionId%3D10003%26oauth_consumer_key%3Djira%253A291ebdb7-1380-4278-98b6-822ca5097c79%26oauth_nonce%3D12164108535489%26oauth_signature_method%3DRSA-SHA1%26oauth_timestamp%3D1451899950%26oauth_token%3D16kBrLuoNLWmM6F2fopoG4h6frbGYccQ%26oauth_version%3D1.0, oauth_signature_method=RSA-SHA1}"
      

      Workaround

      Trigger builds with an account without umlaut characters in the full name

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dlee@atlassian.com Deric Lee (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: