Hello Alexander,

I made changes you've proposed in the first and second patches. You
may get an SVNKit build with these modifications includes at
http://teamcity.tmatesoft.com/viewLog.html?buildId=5201&tab=artifacts&buildTypeId=bt43
Please let me know if this build works for you.

Regarding third modification you propose, I think I'd rather not apply
it. The idea behind using native Windows API to get NTLM
authentication token to use, is that Windows will take responsibility
of prompting user fro credentials if necessary or, in most case, it
should just use already available information it has, as in most cases
user is already logged into the OS with his or her domain credentials.

I'll review the code we use to interact with the native Windows API to
see if there is any potential problem and would appreciate your help
with testing new builds.
Thanks!

Alexander Kitaev,
TMate Software,
http://subgit.com/ - Svn to Git Migration!
http://svnkit.com/ - Java [Sub]Versioning Library!
http://hg4j.com/ - Java Mercurial Library!
http://sqljet.com/ - Java SQLite Library!


On 31 January 2013 11:12, Alexander Dreweke
<alexander.drew...@methodpark.de> wrote:
> Hi
>
> we are trying to use SVNKit to connect to an svn server (svn 1.7) using
> NTLM-only authentication. As the users and the servers don't belong to
> the same domain, we perpended the domain to the username using '\' as
> separator. Nevertheless tcpdump showed, that no domain was transfered to
> the server.
>
> I've attached 2 patches that address this error(s):
> 0001-domain-must-be-determined-from-complete-username.patch
> 0002-carry-over-the-complete-username.patch
>
> Afterwards the authentication worked with the SVNKit own NTLM
> implementation, but switching to Windows native authentication via
> -Dsvnkit.http.ntlm=jna still resulted in authentication errors.
>
> Using native auth mechanism without calling auth providers first,
> doesn't work at all for us. With this the client transmits the hostname
> as username, receiving an authentication error and not trying again with
> the provided username and password. I'm not quiet sure if this is the
> right way to address this, but it works for our setup:
> 0003-native-auth-without-auth-provider-doesn-t-work.patch
>
> I hope you could apply patch 0001 and 0002, and have another look at
> 0003.
>
> Regard
>         Alexander
> --
> Dr. Alexander Dreweke, Software Engineer
> Method Park Software AG, Wetterkreuz 19a, 91058 Erlangen, Deutschland
> Tel.: +49 9131 97 206-443 alexander.drew...@methodpark.de
> Fax:  +49 9131 97 206-200 www.methodpark.de
>
> Vorstand:
> Prof. Dr. Bernd Hindel (Vorsitzender), Dr. Martin Geier, Dr. Erich Meier
> Aufsichtsratvorsitzender: Klaus-Magnus Junginger
> Sitz der Gesellschaft ist Erlangen
> Registergericht Fürth, HRB 8609

Reply via email to