On 07.08.2013 10:04, Simon Large wrote:
> On 7 August 2013 08:53, Elias Gerber <eg_at_viscomvisual.com> wrote:
>> Since we've updated to tortoise 1.8 'Basic authentication' is no longer
>> working: In our server (Visual SVN Server) we've set up to 'Use Windows
>> authentication' and then checked
>> 'Basic authentication'
>> 'Integrated Windows authentication'
>> With Tortoise SVN Clients <= 1.7 we had the behavior that the clients
>> first tried 'Integrated Windows authentication'. If that did not work,
>> it tried 'Basic authentication': A pop-up message appeared, allowing us
>> to enter username/password. We used that for clients that were not part
>> of the Windows domain: The windows authentication failed (as the domain
>> control could not be reached) and the user was able to do 'Basic
>> Since Tortoise SVN Client only 'Integrated Windows authentication' seems
>> to work: Computers inside the domain can authenticate fine, without the
>> need to enter username/password. But computers outside the domain can
>> never enter username/password: We get a message-box about the
>> certificate to accept, and then authentication just fails, without the
>> possibility to enter username/password.
>> With an 1.8 Tortoise SVN client we have this behavior if we try to
>> connect to a visual svn server using svn v1.7 or v1.8.
>> With a 1.7 Tortoise SVN client everything works, no matter if the svn
>> server uses svn 1.7 or v1.8.
>> We have cleared all "saved data", this does not resolve the problem.
>> Anyone an idea?
> Are you using 1.8.0 or 1.8.1? Some auth problems were fixed in 1.8.1,
> though there may be more to come. Almost certainly this comes from a
> change in subversion, which now uses serf in place of neon as the http
> library. (serf was optional but not the default in 1.7, but in 1.8 it
> is the only choice).
We have the problem with the Client 1.8.0 and 1.8.1.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-07 10:41:04 CEST