dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Error using last auth provider.

( SVNCOM )
Type: Public Status:Closed Created: 13 Nov 07 11:00 Updated: 19 Nov 07 11:00
--> Igor Pushkov (admin)  at 19 Nov 07 11:00 writes

SVNCOM library uses some special "tricks" to optimize amount of
authentications request. The key part of this functionality is
PushOkSvn.SVNAuthManager. By default it is not supposed to used publicly.
However error which happens for you might be caused by some incorrect usage
of this object so I'll explain how it works.
1. When SVNClient object created it hiddenly "creates" SVNAuthManager which
is unique object per the same process.
2. Then if you call function SetupAuth (0) or didn't call it at all
SVNClient asks SVNAuthManager to create new authentication object. This
object is some internal SVN client library object which is stored in
SVNAuthManager and identified by some integer cookie (identity).
3. At the later time this cookie can be used to instruct another instance
of SVNClient to use the same authentication object. This demostrated in
this sample:
set client1 = CreateObject("PushOkSvn.SVNClient")
client.SetOption SvnClientOptionDefUserName, "User"
client.SetOption SvnClientOptionDefUserPassword, "Password"
set client2 = CreateObject("PushOkSvn.SVNClient")
dim authcookie
' ask first client to setup new auth object and return its cookie
set authcookie = client1.SetupAuth 0
' ask second client use the same auth as first one
client2.SetupAuth authcookie
4. If you destroy SVNClient object for which you initially obtain
authentication cookie you can ask SVNAuthManager to do not destroy
authentication object by calling AddRefAuthProvider(authcookie).
5. Exist few options for SetOption function which control how authetication
occurs:
- SvnClientOptionAuthInteractiveOnly -- don't cache authentication, ask
user
- SvnClientOptionAuthNonInteractive -- never ask user, used cached only
Mentioned error might appear when for some reason SVNCLient knows some auth
cookie (refference to authentication object in AuthManager) which is not
longer valid. Authcookie can appears invalid in following cases:
1. For some reason SVNAuthManager instance was destoryed between calls to
SVNClient functions. To avoid this you can globally declare and create
SVNAuthManager.
2. Because of bug in SVNClient with non initialized variable. It is fixes
few months ago and fix should exist in latest version. However SetuAuth (0)
should solve issue not depending on does your version have this fix or not.
--> Duboeuf Stéphane (user)  at 19 Nov 07 11:00 writes


Hello,
I downloaded the version 1.4.5.5 (SDK installation) on your web site, and I
have included the svncom.dll in my solution.
The dll which appears in my solution is named "Interop.PushOkSvn.dll", it's
indicated version 1.3.0.0.
I'm doing some bunch of operations as one logical operation and I have
tested your solution but I've got the same problems. Some times an
operation fail without reason (and not always the same). Once it had failed
one time it starts to bug, the library become very unstable and a lot of
operation failed. An "iisreset" help to stabilize the library.
I suppose it's due to the way of connected. I saw that your library is
using cookies to store the connection. Is there a way not to use cookie and
to create a new connection each time?
I'm using "svnClient.SetupAuth(0);" to try to initialize the connection,
but I'm not sure it's the good method.
Thanks!
Stephane
-----Message d'origine-----
De : support@pushok.com [mailto:support@pushok.com]
Envoyé : vendredi 16 novembre 2007 09:33
À : Duboeuf Stephane
Objet : [pst1853] Error using last auth provider.
Can you provide version of SVNCOM bindings you using?
Also, if you doing bunch of operations as one logical operation it is
preferable to cache authentication as described here:
http://www.pushok.com/soft_svncom.php
--> Igor Pushkov (admin)  at 16 Nov 07 11:00 writes

Can you provide version of SVNCOM bindings you using?

Also, if you doing bunch of operations as one logical operation it is
preferable to cache authentication as described here:
http://www.pushok.com/soft_svncom.php
--> Duboeuf Stéphane (user)  at 13 Nov 07 11:00 writes

Hello,

I'm using your SVNCOM library for a C# project and I have some problems
with the connection.

I'm connecting svn this way :
------------------------------------------------------------------------------
UserProcessor processor = new
UserProcessor(Common.Configuration.Configuration.GetConnectionString("ConnectionStringCGP"));
List usr = processor.GetSVNUserInfo(userId);
SVNClientClass svnClient = new PushOkSvn.SVNClientClass();

svnClient.SetOption(PushOkSvn.SvnClientOption.SvnClientOptionDefUserName,
usr[0].Login);

svnClient.SetOption(PushOkSvn.SvnClientOption.SvnClientOptionDefPassword,
usr[0].Pwd);
svnClient.InitClient();
return svnClient;
------------------------------------------------------------------------------

I'm creating a new SVNClientClass each time I've got to do an action on SVN
(check-out, commit, import...) and some times I have this error : "Error
using last auth provider."

Is there a way to avoid this error? To clean the object?

Thanks you very much.
Regards,
Stéphane
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9536671 visitor since 20 Jan 2003.
1229 visitors today and 1 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com