This post is more than 5 years old
5 Posts
0
4678
March 31st, 2020 01:00
Brocade with LDAPS authentication
hi All,
our environment need to use LDAPS authentication using port 636 instead of 389.
Is it a supported configuration?
i have configure aaaconfig and ldapcfg --maprole and when i login using 636, i got error: unable to get local issuer certificate
Next i configure seccertmgmt import -ca -server/client ldap ca cert which is successful and error i got is unable to authenticate my AD user account.
Next i tried seccermgmt import -cert ldap, but system tell me i dont have ldap key, ask me to generate ldap key and csr.
Do i go ahead and create ldap key and csr? because there is a prompt saying by creating CSR:
1) Delete all existing csr
2) Delete existing switch certificates
3) Reset the certificate filename to none.
I have already configured HTTPS certificates and don't wish for all my HTTPS certs to be gone.
Please advise how can i authenticate using port 636 and Thanks so much,
2) Delete existing switch certificates
3) Reset the certificate filename to none.
I have already configured HTTPS certificates and don't wish for all my HTTPS certs to be gone.
Please advise how can i authenticate using port 636 and Thanks so much,
No Events found!
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.5K Points
0
April 1st, 2020 09:00
Thanks,
The manual doesn’t show anything about supporting LDAPS, just regularly LDAP. https://dell.to/2X0dAIY
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.5K Points
0
March 31st, 2020 09:00
Hi,
Which switch are you using?
leng20021976
5 Posts
0
March 31st, 2020 20:00
hi Josh,
we are using 6520 and FOS is 8.2.1c