Skip to content
This repository has been archived by the owner on Jul 24, 2023. It is now read-only.

SSL working but TLS not #905

Open
Debkronisz opened this issue Dec 1, 2020 · 0 comments
Open

SSL working but TLS not #905

Debkronisz opened this issue Dec 1, 2020 · 0 comments

Comments

@Debkronisz
Copy link

Debkronisz commented Dec 1, 2020

  • Laravel Version: 7.16.1
  • Adldap2-Laravel Version: 6.1.4
  • PHP Version: 7.3.21
  • LDAP Type: ActiveDirectory

Description:

Hi,
my name is George.

How to connect to LDAP Server with TLS?
What is name contents in custom_options, the path of CA cert?

Can you help me?
Thank you very much!

Steps To Reproduce:

port: 389
When connect to server on port 389, everíthing is all right.

port: 3269 with only SSL
When connect to server with I'm using this configuration at below:

.env
	LDAP_USE_SSL=true
	LDAP_USE_TLS=false
	LDAP_PORT=3269

ldap.php
    'port' => env('LDAP_PORT', 389),
    'use_ssl' => env('LDAP_USE_SSL', false),
    'use_tls' => env('LDAP_USE_TLS', false),

    //  'custom_options' => [
    //     LDAP_OPT_X_TLS_REQUIRE_CERT => LDAP_OPT_X_TLS_NEVER
    //  ],
    OR
        'custom_options' => [
            LDAP_OPT_X_TLS_REQUIRE_CERT => LDAP_OPT_X_TLS_NEVER
        ],

log
    local.INFO: LDAP (ldaps://server-name:3269)
    has been successfully found for authentication.

then everíthing is all right too.

port: 3269 with SSL and TLS

.IF,
    .env
        LDAP_USE_SSL=true
        LDAP_USE_TLS=true
        LDAP_PORT=3269
    ldap.php
        unchanged
    log
        local.INFO: LDAP (ldaps://server-name:3269)
        has been successfully found for authentication.

then everíthing is all right too, but missing cacert path, so this is wrong.

port: 3269 with only TLS

.BUT,
    .env
        LDAP_USE_SSL=false
        LDAP_USE_TLS=true
        LDAP_PORT=3269
    ldap.php
        unchanged
    then I got has an error -> Reason: Can't contact LDAP server
    It seems to me, is problem here? or has the problem this key:
    log
        local.WARNING: LDAP (ldap://server-name:3269)

so it wasn't using the ldaps to connect.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant