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

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 5.3.2
    • Affects Version/s: 5.3.0, 5.3.1
    • Component/s: Applications
    • None
    • 5
    • Severity 2 - Major
    • 47

      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. 

            Assignee:
            Viktar Arlou
            Reporter:
            Saurabh Bhatia
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: