I would like to make an SSL connection to our LDAP directory from Stash, however the certificate the LDAP server is using, is not matching the DNS registration. And it's not an option to change it, because it involves too many dependencies from other systems using LDAP.
I think it's a bad idea to change the hosts file, so I the Data approach and changed the connection to LDAPS and port 636 + set the value ldap.secure to false. It partly worked (see attached screendump of the LDAP connection).
Can I fix this by change some values in the Database ?
BTW it would be nice if Stash had a setting to disabled Host Name validation. I've seen it done in other Java applications ;-)
Well If you read my question, a new certificate is not an option, and SSL must not match the DNS entry, this is only a security setting to prevent false certicates.
In a controlled environment you kan easily in JAVA disable the hostname validation. All I'm asking is a setting, so I can decide whether or not, host name validation should be enabled.
And I think Stash might have a bug, since 5 out of 6 steps was working when enabling LDAPS, only user authencation failed.
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs