Connect Windows Active Directory through LDAP or LDAPS to make directory user management more efficient.
Reduce manual directory-user administration
Employee changes require administrators to maintain accounts in both Active Directory and LynxPDF, increasing the risk of missed access updates.
A mismatch in the directory host, port 389 or 636, read-only bind account, CA certificate, or network access can cause the connection to fail or prevent certificate trust from being established.
Administrators must review user mappings, organization membership, and license assignments; otherwise, synchronized users may still lack access or may receive licenses incorrectly.
See what LynxPDF supports and how it helps teams manage PDF access.
Use LDAP on port 389 or LDAPS on port 636 based on directory and transport-security requirements.
Explore SolutionsVerify the directory host, ports, bind account, certificates, network access, and user mappings. Directory sync does not replace AD governance or assign licenses automatically.
LynxPDF supports Windows Active Directory connections through LDAP or LDAPS.
IT controls the directory host, ports, read-only bind account, and user mapping.
LDAPS can use a CA certificate to verify the directory server trust chain.
Prepare the directory host, port 389 or 636, and a read-only bind account.
Prepare the CA certificate and network access when LDAPS is required.
Test the connection and review synchronized users before assigning access.
Follow a clear path from setup through verification.
Prepare Windows AD details and a dedicated read-only bind account.
Use LDAP on port 389 or LDAPS on port 636, and configure the directory connection for your environment.
Configure parameters and upload a CA certificate when LDAPS trust requires it.
Test the connection, synchronize users and review the directory-user list.
Reduce directory maintenance and make connection requirements and licensing boundaries easier to review
A tested directory connection and synchronized user list give IT a clearer foundation for controlled LynxPDF access management.
Use confirmed directory and access settings so IT can verify synchronization and access results.
Have the responsible administrator confirm the environment, permissions, version, and final rollout scope.
See how LynxPDF fits enterprise workflows compared with common PDF tools
Support Windows Server, Intune, GPO, RDS, and SCCM deployment approaches for different devices and IT requirements.
Fit restricted-network or local data-management scenarios with a local or cloud deployment path.
Bring Admin Console, SSO, license management, and bulk deployment into one enterprise workflow to reduce repeated configuration and maintenance across systems.