php ldap Connections after Server Change

By -

I am decommissioning our old web server that is hosting our OFFLINE website that uses LDAP for logins.

The site is running on XAMPP and I have copied over all the databases and the web site to the new server. I am upgrading from XAMPP 8.0.0.0 to XAMPP 8.2.4. I am only using Apache and MySQL. I can get to the site but I am unable to authenticate with LDAP as I can with the old server. In the code for the authentication it will not bind. I am not sure why. LDAP servers have been restarted since turning on the new server and getting it in place. People are able to login through A/D on their machines without a problem.

function authenticateUser($user, $password) {
        $host = "DC01";
        $domain = "DOMAIN.NET";
        $basedn = "dc=DOMAIN,dc=NET";
        $group = "Users";
        $ad = ldap_connect("ldaps://{$host}.{$domain}:636") or die('Could not connect to LDAP server.');
        ldap_set_option($ad, LDAP_OPT_PROTOCOL_VERSION, 3);
        ldap_set_option($ad, LDAP_OPT_REFERRALS, 0);
        if (@ldap_bind($ad, "{$user}@{$domain}", $password) == TRUE) {
            $userdn = ldapGetDN($ad, $user, $basedn);
            if (ldapCheckGroup($ad, $userdn, ldapGetDN($ad, $group, $basedn))) {
                // echo "Your're authorized as ";
                $userCheck = 1;
            }
            else {
                // echo "Authorization failed";
                $userCheck = 0;
            }
        }
        else {
            // echo "Could not bind to AD ";
            $userCheck = 0;
        }
        return $userCheck;
    }

XAMPP extensions I have ldap enabled but it won't authenticate. It looks like it goes to the else and not the if (@ldap_bind($ad, "{$user}@{$domain}", $password) == TRUE) {

What am I missing for the Authentication? The server has a valid cert issued by the CA.

UPDATE: Checked the php.ini and the 8.2.4 has a not about putting the extension=ldap must be before the extension=curl if OpenSSL1.0.2 or OpenLDAP is used or it results in a segfault when unloading after using SASL. So I have ldap after curl. Either way I am still getting a bind error. Bind I am unable to bind.



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more