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

XMLWordPrintable

    • 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. 

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

            aanastasov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Ahmad Faridi made changes -
            Description Original: h3. 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 -
            {noformat}
            java.lang.IllegalArgumentException: Failed to parse address AA.*.*.*
            {noformat}
             
            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # [Create an application under Crowd|https://confluence.atlassian.com/crowd/adding-an-application-18579591.html]
             # In the View Application screen, click the Remote Addresses tab and update the Address field to include IP address range such as {noformat}172.16.*.*{noformat}

            h3. 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

            h3. Actual Results

            The below exception is thrown in the atlassian-crowd.log file:
            {noformat}
            java.lang.IllegalArgumentException: Failed to parse address AA.*.*.*
            {noformat}

            h3. Workaround
             Currently there is no known workaround for this behavior. A workaround will be added here when available             		New: h3. 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 -
            {noformat}
            java.lang.IllegalArgumentException: Failed to parse address AA.*.*.*
            {noformat}
            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # [Create an application under Crowd|https://confluence.atlassian.com/crowd/adding-an-application-18579591.html]
             # In the View Application screen, click the Remote Addresses tab and update the Address field to include IP address range such as
            {noformat}
            172.16.*.*{noformat}

            h3. 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]
            h3. Actual Results

            The below exception is thrown in the atlassian-crowd.log file:
            {noformat}
            java.lang.IllegalArgumentException: Failed to parse address AA.*.*.*
            {noformat}
            h3. Workaround

            Replace the wildcard notations with CIDR subnet notation instead. 
            SET Analytics Bot made changes -
            UIS Original: 39 New: 47
            SET Analytics Bot made changes -
            Support reference count Original: 4 New: 5
            SET Analytics Bot made changes -
            UIS Original: 14 New: 39
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            UIS Original: 5 New: 14
            SET Analytics Bot made changes -
            UIS Original: 4 New: 5
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS New: 4

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

                Created:
                Updated:
                Resolved: