... ... ``` Save and close Web.config ### **Start aqua Server** After configuration, you can start your aqua server. Go back to IIS-Manager and start 'aquaAPIPool, 'aquaFileServerPool', 'aquaWebservicePool'.\ \ \ **Configuring multiple LDAP servers**\ You can connect up to 50 different LDAP servers with aqua. Each will be checked one-by-one, when authenticating the users. The configuration can be extended by adding a proper index in the key names of the configuration. The indexes will define, in which order the servers are taken for authentication. You can give any index you like, from 1-50, for example: {% code overflow="wrap" %} ```xml ``` {% endcode %} In order to configure multiple servers, just copy the configuration as often as needed and change the indexes and addresses. We keep backward compatibility with previous configuration. Old configurations will work without the necessity to change them. ### Active Directory Authentication Module The Active Directory authentication module can be activated by providing the `ActiveDirectory.Domain` in aqua server parameter configuration. Please see the [aqua server parameters](/documentation/installation-for-on-premise/server-parameters.md) for more details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aqua-cloud.io/documentation/integrations/sso/ldap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.