Menu

#209 Common Password for all projects

New
nobody
None
Medium
Enhancement
2018-07-19
2009-10-05
Anonymous
No

Originally created by: AndrewA....@gmail.com

In our company we can have many projects on the go at anyone time and
within each project there are several SVN projects.
So when we have to change our password (every 30 days) we have to edit
each project (in my case that means approx. 30 SVN projects) in the Commit
Monitor before it does another check or take the chance that our user id
gets locked out because of too many wrong password attempts.

What is the expected output? What do you see instead?
I would like to see one common password for all projects, but also have an
override on a per project basis if needed.

What version of the product are you using? On what operating system?
1.6.5 on Windows XP Pro

Please provide any additional information below.

Thanks
Andrew

Related

Tickets: #91

Discussion

  • Anonymous

    Anonymous - 2009-10-06

    Originally posted by: tortoisesvn

    (No comment was entered for this change.)

    Labels: -Type-Defect Type-Enhancement

     
  • Anonymous

    Anonymous - 2010-04-09

    Originally posted by: PiotrOws...@gmail.com

    This is actually the most anticipated feature for me.
    This would make my life a lot easier.

     
  • Anonymous

    Anonymous - 2010-04-13

    Originally posted by: mr.ber...@gmail.com

    Yes! Very useful feature. I constantly get locked out of our SVN server whenever I
    change my password (which is a very global password, for all kinds of things).

     
  • Anonymous

    Anonymous - 2010-04-27

    Originally posted by: pjohnme...@gmail.com

    As far as editing your projects go, if you let svn cache your credentials, and simply
    do not enter your username and password in Commit Monitor, you will not have to edit
    your 30 projects.  You will, however, have to do an authenticated action in your client
    of choice so the new password will get cached.

    You are right, though, that you could still get locked out if too many projects tried
    to update with the old credentials before you got around to making the change.

     
  • Anonymous

    Anonymous - 2010-05-04

    Originally posted by: thomas.o...@gmx.de

    It would be great if Commit Monitor (also TortoiseSVN) could use the credentials from
    the actual logined user. In our company the password must be changed every 30 days.
    The main problem is that our user acounts are deactivated after 3 wrong User/password
    connects. So now the IT does not longer allow us to use the CommitMonitor because
    they had to often to activate the user accounts in the ActiveDirectory.

    Hope that it would possible to realize this feature

     
  • Anonymous

    Anonymous - 2010-06-21

    Originally posted by: tortoisesvn

    Thomas: both TSVN and CM use SSPI authentication (i.e., your windows login data) if your server is set up to use and *ask* for it. If they don't, then you haven't set your server up correctly.

     
  • Anonymous

    Anonymous - 2011-04-15

    Originally posted by: mhader...@gmail.com

    Wow I had no idea that if you left your username and password blank it would just use your windows credentials. You should put this on somewhere prominent on the homepage.

     
  • Anonymous

    Anonymous - 2011-04-15

    Originally posted by: goo...@taeguk.co.uk

    Or on set settings Dialog - it works a treat :D

     
  • Anonymous

    Anonymous - 2011-04-16

    Originally posted by: tortoisesvn

    if you leave username/password blank, it only works if your server is set up to use SSPI authentication. In that case, you don't need username/password since the authentication is done using your Windows logon credentials.
    But that has nothing to do with CM but only with the authentication setup.

     
  • Anonymous

    Anonymous - 2012-03-17

    Originally posted by: eric.hub...@googlemail.com

    I would prefer an account management, so that the user can save multiple username/password combinations and optionally associate an account with projects. This way there is a central place to change passwords affecting all projects where this account is used.

     
  • Anonymous

    Anonymous - 2012-08-08

    Originally posted by: adammar...@gmail.com

    Any update on this?  What a pain to have to reset all these passwords, especially considering you cannot copy-paste the password.

     
  • Anonymous

    Anonymous - 2013-10-17

    Originally posted by: joseph.t...@gmail.com

    I fully agreed to have one common password for all project as the base and can be override by individual sub project.  I have similar scenario with Andrew that my company policy of changing password every month and our Svn server is authenticated via Windows Active Directory.  I am currently looking at 10 repositories with different branches and trunk, is a pain in the butt to Edit each project in order to change my password.

     
  • thilo20

    thilo20 - 2016-02-19

    feature "Default Authentication" is supported since version 1.11.1, for screenshots see https://sourceforge.net/p/commitmonitor/tickets/462

     

    Last edit: thilo20 2016-02-19
  • Karen Arzumanyan

    Very need options for windows authentication. As default and for each project. Actual for AD authentication.

     

Log in to post a comment.