When configuring Confluence/JIRA to Crowd there's a Test settings button.
      This will do a call to Crowd with the following settings.

      URL: crowd/rest/usermanagement/1/search?entity-type=user&start-index=0&max-result=1&expand=user
      HTTP Method: POST
      Content-Type: application/xml
      Body:
      <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
      <null-search-restriction/>

      As you can see in the URL, it's supposed to get a max-result of 1.

      I get a result of all the users I have configured when doing this call manually. This also results in a timeout when having a Crowd application with over 2000+ users.

            [CWD-3180] Test connection result limit parameter ignored

            Hi,

            We're using JIRA 4.2.8, I don't have access to the network at the moment. Also, am I right that on database level this call still performs a select * from cwd_user? I can't put any logging on the database, locally I'm, running the standalone version and production is in the Amazon Cloud where you only have an error log.. Performance wise it would be absurd to still select all the users including the joins and then narrow it down to a single user, although I can't confirm this.

            Patrick van der Rijst added a comment - Hi, We're using JIRA 4.2.8, I don't have access to the network at the moment. Also, am I right that on database level this call still performs a select * from cwd_user? I can't put any logging on the database, locally I'm, running the standalone version and production is in the Amazon Cloud where you only have an error log.. Performance wise it would be absurd to still select all the users including the joins and then narrow it down to a single user, although I can't confirm this.

            joe added a comment -

            I'm seeing:

            POST /rest/usermanagement/1/search?entity-type=user&start-index=0&max-results=1&expand=user HTTP/1.1
            Accept: application/xml
            Authorization: Basic XXXXXXXX
            User-Agent: Jakarta Commons-HttpClient/3.1
            Host: XXXXXXXX
            Content-Length: 83
            Content-Type: application/xml
            
            <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
            <null-search-restriction/>
            

            Can you please confirm the exact version of Confluence or JIRA that you're using and, if possible, include a network dump of the request?

            joe added a comment - I'm seeing: POST /rest/usermanagement/1/search?entity-type=user&start-index=0&max-results=1&expand=user HTTP/1.1 Accept: application/xml Authorization: Basic XXXXXXXX User-Agent: Jakarta Commons-HttpClient/3.1 Host: XXXXXXXX Content-Length: 83 Content-Type: application/xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <null-search-restriction/> Can you please confirm the exact version of Confluence or JIRA that you're using and, if possible, include a network dump of the request?

            For the Test Connection I mean.

            Patrick van der Rijst added a comment - For the Test Connection I mean.

            You're right! The problem is then, that JIRA/Confluence use the max-result parameter, which causes a time-out for us because there are so many users.

            Patrick van der Rijst added a comment - You're right! The problem is then, that JIRA/Confluence use the max-result parameter, which causes a time-out for us because there are so many users.

            joe added a comment -

            The query parameter should be 'max-results', with an 's'; I've just checked it and I only get the expected single result. Can you confirm whether Test Settings is using that correct parameter name?

            joe added a comment - The query parameter should be 'max-results', with an 's'; I've just checked it and I only get the expected single result. Can you confirm whether Test Settings is using that correct parameter name?

              Unassigned Unassigned
              5b8fbcaff108 Patrick van der Rijst
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: