You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unable to join my self-hosted LDAP server (OpenLDAP) via LDAPS. It seems the issue is the certificates I am using on the LDAP server are self-signed and so Zitadel does not view these as 'secure enough'.
The specific Error is: LDAP Result Code 200 "Network Error": tls: failed to verify certificate: x509: certificate signed by unknown authority
I believe the options to "work through" this is either:
Add the certificates as trusted by Zitadel
Add an option in the LDAP Identity Provider configuration to ignore/trust certificates signed by unknown authorities
Any help to resolve this would be great! Thank you in advance
To reproduce
The specific Error is: LDAP Result Code 200 "Network Error": tls: failed to verify certificate: x509: certificate signed by unknown authority
Screenshots
No response
Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Environment
Self-hosted
Version
No response
Database
CockroachDB
Database Version
No response
Describe the problem caused by this bug
I'm unable to join my self-hosted LDAP server (OpenLDAP) via LDAPS. It seems the issue is the certificates I am using on the LDAP server are self-signed and so Zitadel does not view these as 'secure enough'.
The specific Error is:
LDAP Result Code 200 "Network Error": tls: failed to verify certificate: x509: certificate signed by unknown authority
I believe the options to "work through" this is either:
Any help to resolve this would be great! Thank you in advance
To reproduce
The specific Error is:
LDAP Result Code 200 "Network Error": tls: failed to verify certificate: x509: certificate signed by unknown authority
Screenshots
No response
Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: