Issue description     

When attempting to create or modify a user via the ADManager Plus API, users may encounter the following error:

{
  "statusMessage": "The given select parameter is invalid",
  "status": "SEVERE"
}

This happens when the select parameter does not match the expected format or attribute name in the API request.

Possible causes     

1. Incorrect parameter name: Using a display name instead of an LDAP attribute name (e.g., Username instead of sAMAccountName).

2. Invalid syntax: Including spaces or special characters in the parameter value.

3. Missing required fields: Not specifying mandatory attributes for user creation or modification.

4. Misconfigured API request: The API request does not follow the correct structure.

Prerequisites  

• Ensure ADManager Plus API access is enabled.

• Use LDAP attribute names (e.g., sAMAccountName, givenName, or sn).

• Validate API requests before sending them.

• Ensure that special characters and spaces are only used in parameters where they are permitted and are properly encoded if required.

• Refer to the ADManager Plus API documentation for correct formatting.

Resolution     

Step 1: Validate API request

1. Use tools like Postman to send test requests and verify that the request format is correct and accepted by the API.
   

Step 2: Verify parameter names and consult API documentation

1. Ensure you are using the correct LDAP attribute names, such as sAMAccountName, mail, and displayName.
   
2. Cross-check all parameter names and required fields against the API documentation to avoid errors.
   

Step 3: Check parameter syntax

1. Confirm that the parameter values do not contain spaces or special characters that could cause the API to reject the request.

Step 4: Include required attributes

1. Make sure all mandatory attributes needed for user creation or modification are included in the request payload.

Tips 

• Always use LDAP attribute names instead of display names in API requests.

• Validate and test API calls in a controlled environment before deployment.

• Implement error handling to manage unexpected failures.

How to reach support