Prerequisites for the Nodinite LDAP Web API
This page describes the prerequisites for successfully installing and hosting the Nodinite LDAP Web API.
Instances of the Nodinite LDAP Web API must be installed on-premise on a Windows Server with IIS, or in the cloud/off-site if the target server is placed on a network with access to the LDAP catalog. You can also host the LDAP Web API inside your App Service Environment.
|What rights does the client for Nodinite LDAP Web API require?|
|What Access Rights Does the Nodinite LDAP Web API Require?|
|What Firewall settings are required for the Nodinite LDAP Web API?|
|ASP.NET Core||ASP.NET Core 5.0|
|:fa-globe IIS||If you host the API in IIS, then the App Pool must be a named account with read/write rights to the folder where the binaries are located|
You must use a modern broswer like Edge or Chrome. Add
/swagger last in the address to test it out.
You must have ASP.NET Core installed (a reboot after installation is required)
- Host ASP.NET Core on Windows with IIS)
You should review the Disable PAC Verification user guide and consider the changes required for better performance
If you host the Nodinite LDAP Web API in IIS, then you must install the following components:
Windows 2012 R2
You can host the Nodinite LDAP Web API in an Azure App Service Environment
Cloud technologies are evolving fast and as Microsoft deprecates older versions of their Services and API's now and then. Nodinite will always support the API's supported by Microsoft. This means you need to update the Nodinite LDAP Web API from time to time.
Make sure to subscribe to the Release Notes
The code, or the system integration platform uses an identifier (a guid) to identify which connection to use, executing a LDAP statement. The API is not secured in anyway but you should use HTTPS and you can further restrict access by white listing IP addresses.
- The account being used for the LDAP queries must have proper read/write access to targeted objects in the LDAP/AD catalog.
- The server must be domain joined, and you must target Active Directory, if you do not provide explicit connection information in the adapter.
For a complete list of ports, review the TCP and UDP ports user guide. The following ports must be always be allowed:
|53||DNS||The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file)|
The Nodinite LDAP Web API has both inbound and outbound communication:
- Between the Client/Consumer and the Nodinite LDAP Web API
- Between the Nodinite LDAP Web API and the LDAP Catalog Service (Active Directory, Novell, NIS, DIRX, ...)
|443||HTTPS||Secure inbound traffic with|
|636||RPC for SSL/LDAPS||SSL|