Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

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

Stephen Espy
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?


context stuff:

  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic