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

Requiring TLS/SSL breaks DNS SRV lookup

XMLWordPrintable

      Bamboo claims it will look up the service record for instant messaging if you leave the port blank:

      "If no port is specified, Bamboo will first perform a DNS SRV lookup or use the default port."

      However, if you specify "Requires an TLS/SSL connection" then it will not look up the service record and will use port 5222/5223 and the specified host name instead.

      This seems to be a very longstanding bug.

      Workarounds (not good workarounds):

      • Don't specify requiring a secure connection (a secure connection should still be used if available)
      • Don't use DNS SRV lookup and instead specify the direct host and portname.

            [BAM-15539] Requiring TLS/SSL breaks DNS SRV lookup

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1441462 ] New: JAC Bug Workflow v3 [ 3385313 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Oleksandr Tkachenko made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Oleksandr Tkachenko added a comment -
            Atlassian Update – 3 April 2018

            Hi everyone,
            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Syed Masood
            Bamboo Product Manager

            Oleksandr Tkachenko added a comment - Atlassian Update – 3 April 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Syed Masood Bamboo Product Manager
            Oleksandr Tkachenko made changes -
            Labels New: bamboo-bugs-grooming
            Alexey Chystoprudov made changes -
            Component/s New: Installation [ 11430 ]
            Component/s New: Network [ 34390 ]
            jonah (Inactive) made changes -
            Symptom Severity New: Minor [ 14432 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1417400 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1441462 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 828988 ] New: Bamboo Workflow 2016 v1 [ 1417400 ]
            Daniel (Inactive) made changes -
            Status Original: Needs Triage [ 10030 ] New: Open [ 1 ]

              Unassigned Unassigned
              don.willis@atlassian.com Don Willis
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: