[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Two levels of authentication

From: Mike Scott <mike_at_mikescommunity.com>
Date: 2007-04-17 17:13:34 CEST



I'm new to the list. I've a suggestion and thought I'd try posting it here
for discussion before adding it to the issue tracker. Forgive me if this has
already been discussed and I've missed it.


My suggestion is treating read and write authentication data caching
separately in TSVN. The reason is that I am in a team of devs who use TSVN
and we want to make sure that when we check in, it's with our own
credentials. So we never check the "Save authentication" checkbox in the
login dialog.


However, when viewing the repo, updating, etc. when read-only access us
required, it would be great to remember login details to save incessant
login dialogs every time TSVN hits the repo for information.


IOW, saving authentication data is VERY convenient, but only when performing
operations which don't change the repository. Explicit authentication
should be required for repository changes.


One possible implementation of this would be to split the option to clear
authentication data in the TSVN settings dialog into separate clear
read-only and update authentication data. One could then log in and check
the remember option and immediately clear the credentials for update. Then,
TSVN would only present the login dialog when committing or making other
changes to the repo.


Another option would be to split the "Save authentication" checkbox into
"Save authentication for reading" & "Save authentication for writing"
checkboxes - or similar wording.


Note: anonymous log in isn't acceptable for repository reads, so I can't set
it up this way in the repo config.




Received on Tue Apr 17 17:16:29 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.