aspose file tools*
The moose likes Security and the fly likes Spring/AD authentication ServiceUnavailableException ONLY on ssl 636, not 389 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Security
Bookmark "Spring/AD authentication ServiceUnavailableException ONLY on ssl 636, not 389" Watch "Spring/AD authentication ServiceUnavailableException ONLY on ssl 636, not 389" New topic
Author

Spring/AD authentication ServiceUnavailableException ONLY on ssl 636, not 389

Stephen Espy
Greenhorn

Joined: Feb 25, 2002
Posts: 1
All is well when I try using 389 on the "insecure" server, but when I switch my config over to the secure server I get ServiceUnavailableException. I am bining under an "application" ldap username, and sending a standard username and password in an ldap:



This is an AD server. Ok, the dumb question... I have done nothing with any certificates, keystores, etc. Is this the problem? Do I need a certificate only for the inital bind if I DON'T have an "application" username in ldap to bind with before calling authenticate?

Thanks!


context stuff:


 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Spring/AD authentication ServiceUnavailableException ONLY on ssl 636, not 389