Adding a Version 1 License Key through bamboo.cfg.xml can cause license decoding to fail

XMLWordPrintable

    • Type: Bug
    • Resolution: Handled by Support
    • Priority: Low
    • None
    • Affects Version/s: 6.4.0, 6.5.0, 6.6.1, 6.7.1
    • Component/s: None
    • None
    • Severity 1 - Critical

      Issue Summary

      Some Bamboo licenses are being generated as Version 1 Licenses, which have fewer characters than Version 2 licenses, and can include the character < or >

      Steps to Reproduce

      1. Add a Version 1 license to bamboo.cfg.xml
      2. Start Bamboo

      Expected Results

      Bamboo starts as expected

      Actual Results

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

      2019-01-03 19:51:53,733 FATAL [localhost-startStop-1] [BootstrapLoaderListener] An error was encountered while bootstrapping Bamboo (see below):
Could not find any valid decoders in [com.atlassian.extras.decoder.v2.Version2LicenseDecoder@16214fb7, com.atlassian.extras.decoder.v1.Version1LicenseDecoder@6f00ba8f] for license string <license string here>
com.atlassian.extras.decoder.api.LicenseDecoderNotFoundException: Could not find any valid decoders in [com.atlassian.extras.decoder.v2.Version2LicenseDecoder@16214fb7, com.atlassian.extras.decoder.v1.Version1LicenseDecoder@6f00ba8f] for license string <license string here>

      Workaround

      Please ensure that the < or > characters are encoded, for example if your key includes the string:

      ailuahfUaadbfaalaaussba<akaieiiqoqoqpah

      Update it to

      ailuahfUaadbfaalaaussba&lt;akaieiiqoqoqpah

      Please also ensure that any whitespace (including spaces and carriage returns) in the key is kept as it was in my.atlassian.com.

            Assignee:
            Unassigned
            Reporter:
            Ellie Z
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: