Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

my wildcard certificate doesn't get accepted with ldap 2.4.23. when i try to connect i get the following error:

TLS certificate verification: subject:
cipher: AES-256, security level: high, secret key bits: 256, total key bits: 256,
cache hits: 0, cache misses: 0, cache not reusable: 0
TLS: hostname ( does not match common name in certificate (*

my certificate is: CN=* AND subjectAltName=DNS:*

How can I make it so that my certificate is accepted in LDAP?

share|improve this question
up vote 0 down vote accepted

first i've found a page saying that, wildcards in CN don't work with openldap and you have to use subjectAltName! (I can't find that page anymore...)

unfortunately, i've created the certificate like this, which is not the subjectAltName, that you need:

[ req_distinguished_name ]
subjectAltName                =Alternativer Name 1
subjectAltName_default        =DNS:*

that's why it is displaying OID. instead of subjectAltName...

i've found the answer for subjectAltName on:

After studing of "RFC 2459 - Section Subject Alternative Name" and crossreferencing to the result of isakmpd's certpatch(8) the following should work: [...] To accomplish such an CSR the following entries are needed in the openssl.cnf (please note: I only added the relevant parts for this Attribute)

[ req ]
req_extensions          = v3_req
[ v3_req ]
subjectAltName          =
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.