Table of Contents
Login to FotoWeb is slow when using Active Directory integration (Legacy)
29. April 2025
Table of Contents
If you experience performance issues logging on to FotoWeb using Active Directory integration, these points can help you troubleshoot.
Note: Active Directory integration via LDAP in FotoWeb is set to End of Life from January 1st, 2024, and will be removed from our software in a future version. We strongly recommend switching your identity provider as soon as possible.
Fotoware currently supports a variety of other identity providers, such as Microsoft Entra ID (formerly Azure Active Directory), ADFS + SAML, or any other SAML 2.0 compatible provider, such as Okta, OneLogin, and many more.
Contact Fotoware Support or your Fotoware Partner if you need assistance migrating to a new identity provider.
Possible reasons
- The domain controller is slow to respond.
- Requests to a domain controller are timing out, maybe even deliberately, for security reasons.
How to debug performance issues logging in
Enable additional logging in FotoWeb
- Open the FotoWeb Settings app and go to Settings > System logging.
- Set Application Trace Files to Debug.
- Select Save.
- Reproduce the problem.
- Locate the log file fotoweb.exe Script Processing.trace in the folder C:\ProgramData\Fotoware\FotoWeb\Operations\Logs.
- In the file, search for all lines containing "Search completed in" and with unusually high values (e.g., several seconds).
- Find the corresponding log message "Ldap search..." to locate the LDAP query that was slow.
Possible solutions
- If only lookups of groups or domains that are unnecessary for FotoWeb user authentication are slow, then these queries can be added to the LDAP blacklist.
- Otherwise, this is either an issue with the LDAP server (e.g., load balancing and one or more slow servers) or the network. It has to be resolved by the network administrator.