pombreda / vcscommand

Automatically exported from code.google.com/p/vcscommand
0 stars 0 forks source link

Add username/password prompt or variables to use when underlaying VCS needs them #40

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. checkout a working copy from a repository that requires a specific
username and password for access (read or write). I use subversion 1.5.4.
Configure VCS client to always ask for passwords (storing passwords would
defeats a password's purpuse...)
2. :VCSCommit or :VCSUpdate
3. VCS responds with 'VCSCommand:  Version control command failed: svn:
Can't get user name or password' in red on the status line

What is the expected output? What do you see instead?
I would expect an username and password prompt whenever needed, or some
username/password variables in VCSCommand for me to set, instead of the svn
error message

What version of the product are you using? On what operating system?
Ubuntu 9.04 netbook
Subversion 1.5.4
Vim 7.2
VCSCommand 1.99.31

Please provide any additional information below.
Some --username and --password argument to :VCSCommit might also help ...

Original issue reported on code.google.com by terminatorul@gmail.com on 12 Oct 2009 at 11:09

GoogleCodeExporter commented 9 years ago
I suspect most of the plugin's users already cache their VCS passwords, and 
rely on
their workstation's security.

Would you want to enter the user / password for each command, or once per 
session? 
It might be possible to catch that error and request the user/password and 
explicitly
send them.

Patches are welcome.

Original comment by bob.hies...@gmail.com on 30 Oct 2009 at 7:01

GoogleCodeExporter commented 9 years ago
On each command.

Once per session would be a good option for most people, but I would still keep 
the
plugin to ask on each command. It's not always I need a repository access 
command.
In svn the diff and status commands operate on the working copy only.

I would patch it (to at least accept --username/--password as command 
arguments) but
I would need to learn vim scripting language first ...

Original comment by terminatorul@gmail.com on 30 Oct 2009 at 10:50

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Here is a patch (against v1.99.46, the current git HEAD) to add a Vim prompt 
for username and password when needed, and also a prompt to trust a server 
certificate when issuer is not know.

Also updated the help file to include the 4 extra configuration options used 
(VCSCommandUsername, VCSCommandPassword, VCSCommandTrustServerCertificate, 
VCSCommandPersistSessionCredentials).

Tested on:
    - Ubuntu 11.10 64-bit, svn 1.6.12, Vim 7.3
    - CentOS 6.3 64-bit, Vim 7.2, svn 1.6.11 and 1.7.4
but should also work on other systems and versions.

Original comment by terminatorul@gmail.com on 5 Sep 2012 at 5:38

Attachments:

GoogleCodeExporter commented 9 years ago
I second the need for this. I use svn over https and choose not to cache my 
password.

Original comment by vex...@gmail.com on 12 Sep 2012 at 10:53

GoogleCodeExporter commented 9 years ago
I third the motion. terminat's patch worked great (GVIM 7.3; Windows 7), once I 
modified it to SVN unified diff format (I used TortoiseMerge to patch). I'd 
like to see this feature rolled into the main branch, if possible.

Original comment by gfix...@gmail.com on 25 Sep 2012 at 12:58