|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

I've upgraded to the latest version of the SVN plugin (version 2.5), and enabled the loggin for it, and this is what is printed upon repository connection attempts:
(NOTE: I've replaced a few server name instances and repo paths with placeholders; <serverName> and <path-to-repo>)
It seems like there is a need for a LoginModule to be configured.
I've also tested other types of authentications, namely java:apache and java:jcifs. However, I don't think the execution reaches the actual authentication code.