Hi, I recently implemented a feature in a v15 application that allows the users to log in to 4D Client via their windows credentials. A script using the LDAP LOGIN command makes a call direct from the client app to the LDAP IP address on port 389. It works well with remote clients as well as 4D client on the set station as 4D server.
However, I am having an issue with log in via web browsers. On login via browser connections, the username and password parameters are passed to the 4D Server and used to authenticate against the same LDAP address and port. Using the same login script as the client login, authentication fails even with the correct credentials. Does any one have an idea why this is so? Why is the LDAP script behaving differently when called from the client and from the server ? Regards Ronnie Tarawerkz ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
