Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-6269

Wildcard IP addresses specified as a part of Application "Remote Address" are not working post upgrade to 5.3

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 5.3.2
    • 5.3.0, 5.3.1
    • Applications
    • None

      Issue Summary

      As per, https://confluence.atlassian.com/crowd/specifying-an-application-s-address-or-hostname-25788433.html, we can specify an application IP address, using a wildcard IP address range as part of Remote Address. Though this was working fine earlier but
      post upgrade to 5.3, this is not working and failing with below error -

      java.lang.IllegalArgumentException: Failed to parse address AA.*.*.*
      

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create an application under Crowd
      2. In the View Application screen, click the Remote Addresses tab and update the Address field to include IP address range such as
        172.16.*.*

      Expected Results

      Wildcard IP address range should work fine as shared under https://confluence.atlassian.com/crowd/specifying-an-application-s-address-or-hostname-25788433.html

      Actual Results

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

      java.lang.IllegalArgumentException: Failed to parse address AA.*.*.*
      

      Workaround

      Replace the wildcard notations with CIDR subnet notation instead. 

          Form Name

            [CWD-6269] Wildcard IP addresses specified as a part of Application "Remote Address" are not working post upgrade to 5.3

            Hi 0cafa6498e3c,

            Thanks for the update! Indeed CIDR subnet mask notation is a newly identified workaround to this issue. We will update the ticket to include it under the known workarounds.

            Ahmad Faridi added a comment - Hi 0cafa6498e3c , Thanks for the update! Indeed CIDR subnet mask notation is a newly identified workaround to this issue. We will update the ticket to include it under the known workarounds.

            Charlie Misonne added a comment - - edited

            Glad I found this bug report. But I think it should have been critical at least.

            Today I upgraded Crowd from 5.1.3 to 5.3.1. After the upgrade nobody could login on Bamboo anymore.

            Reason we had a wildcard IP address in the remote addresses list.

            My solution was to replace the wildcard notation by a CIDR notation. Could be a workaround for others reading this report.

            Charlie Misonne added a comment - - edited Glad I found this bug report. But I think it should have been critical at least. Today I upgraded Crowd from 5.1.3 to 5.3.1. After the upgrade nobody could login on Bamboo anymore. Reason we had a wildcard IP address in the remote addresses list. My solution was to replace the wildcard notation by a CIDR notation. Could be a  workaround for others reading this report.

              14cf4249fcc7 Viktar Arlou
              02495d088b9f Saurabh Bhatia
              Affected customers:
              2 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: