[
https://issues.apache.org/jira/browse/MRM-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Stockhammer updated MRM-1934:
------------------------------------
Fix Version/s: 3.0.0
> javax.naming.AuthenticationNotSupportedException
> ------------------------------------------------
>
> Key: MRM-1934
> URL: https://issues.apache.org/jira/browse/MRM-1934
> Project: Archiva
> Issue Type: Bug
> Components: redback
> Affects Versions: 2.2.1
> Environment: Archiva 2.2.1 deployed as WAR on Tomcat 7
> Reporter: Jörg Delker
> Priority: Major
> Fix For: 3.0.0
>
>
> I've configured the _Redback Runtime Configuration_ to connect a LDAP server.
> Following the (rather sparse)
> [documentation|https://archiva.apache.org/docs/2.2.1/adminguide/redback-runtime-configuration.html],
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
