[MRM-1934] javax.naming.AuthenticationNotSupportedException

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.2.1
• Fix Version/s: 3.0.0
• Component/s: redback
• Environment: Archiva 2.2.1 deployed as WAR on Tomcat 7
• Flags: Important
• Assignee: Unassigned
• Reporter: Jörg Delker
• Created: 03/Jan/17 12:09
• Updated: 10/Mar/19 15:39

Description

I've configured the Redback Runtime Configuration to connect a LDAP server.
Following the (rather sparse) documentation, I left the field for authenticationMethod empty.
The Verify LDAP Changes Button indicated a successful connection the LDAP server afterwards.

Then I wondered what effect that authenticationMethod could have.
Lacking any documentation, I simply tried several values and figured that it obviously triggers the particular SASL authentication methods.
Since I don't want to use SASL but bind PLAIN to the LDAP server, I emptied the field again.
Unfortunately, that didn't restore the previous functionality!
The LDAP access log showed, that Archiva is still using TYPE=SASL rather than TYPE=SIMPLE (which has been used on the initial validation).

This problem was not recoverable via the UI.
After, I manually removed the (emtpy) authenticationMethod tag from archiva.xml, TYPE=SIMPLE was used again and connection succeeded.