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

SVN Proxy freezes while changing source control for VS.NET solution...

( SVNSCC , VS .NET, Latest, Win 2003 Server  )
Type: Public Status:Closed Created: 08 Jun 05 06:00 Updated: 09 Jun 05 06:00
--> Igor Pushkov (admin)  at 09 Jun 05 06:00 writes

1. Issue with authentication and anon access
Our plug-in relays into authentication
cache functions build in into SVN. This functions cache your
credentials on your local PC after first successful access attempt
into repository.
Login operation, which exist in plug-in just call svn list command
(which not change anyhthing in repository) providing your user name
and password.
But, unfortunately this is "readonly" operation, and if your
repository allows anonymous "readonly" access (which is on by
default) auth credentials not cached.
The solution is:
a) Switch off anonymous access (anon=none)
b) Call any write enabled operation from any other client, which will
cause svn to cache auth credentials on your local disk.

1. How to use other name than current user name
The info can be found for example here:
http://www.pushok.com/help/svnscc/index.php?redirect=basic_addtoscc.htm
[VS .NET]
First of all select a user name for accessing to SVN: open the
configuration window Tools\Options\Source Control\Scc provider and specify
the name in the Login ID field. Then right-click on tree root (solution) in
Solution Explorer. Select Add to source control.
--> Sam Piper (user)  at 09 Jun 05 06:00 writes


Another update:

Have managed to work out that the plug-in is using the current Windows
credentials when authenticating. The accounts that we have created on the
UNIX box running the server use the same user names but obviously with
different passwords, so authentication is failing.

This is not an ideal situation for our company at all as we have strict
policies on how passwords are changed. To get around this problem we would
have to ask our UNIX administrators to change the passwords manually, which
they are not happy about doing.

Is there no way of configuring the plug-in to use specific credentials when
challenged by the server? If there isn't then I think this is a feature you
need to add to your product as soon as you can, as it is a real
showstopper. There shouldn't be an assumption that people will be
connecting to a repository using exactly the same credentials as their
Windows account, without at least the capability of providing alternative
credentials if desired.

Can you give me an idea of when this might be addressed in an upcoming
version? We will work around this problem in the meantime.
--> Sam Piper (user)  at 09 Jun 05 06:00 writes

Some additional information:

We were initially using write-only access for certain users on the server.
When we allowed anonymous write, the problems disappeared and we could work
normally.

Obviously authentication/authorization is causing the issue - how can we
configure the proxy to correctly authenticate using the credentials we
provide?

I've tried logging in using the Login button when changing source control
but that doesn't seem to have any effect at all.

Please advise - this is an urgent issue for us.
--> Sam Piper (user)  at 08 Jun 05 06:00 writes


Hi,

We have the following problem with your product that is preventing us from
being able to use our new Subversion repository:

When trying to change source control for a solution that is already in the
repository, the projects bind correctly (screenshot one), but when the
proxy attempts to check in the changes, the proxy freezes with screen shown
in screenshot two.

If I click Cancel in the status window, and commit an empty message, it
shows the error message alert shown in screenshot three. I cannot progress
past this point without getting this error message.

We are not using TortoiseSVN or any other SVN client, and we are connecting
to an SVN repository using the svn:// protocol. The server version is
1.1.4. The configuration of the plugin is the default.

Can you please advise of how we can resolve this?
Screenshot One  Screenshot Two  Screenshot Three 
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9755049 visitor since 20 Jan 2003.
1132 visitors today and 3 online right now.
blank left to top right blank

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