[
https://issues.apache.org/jira/browse/SVN-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14930428#comment-14930428
]
Ivan Zhakov edited comment on SVN-3926 at 10/17/15 6:26 PM:
------------------------------------------------------------
It's definitely better to have a different realm for every repository: users
should know/be told what they are entering their auth data for.
But users have had problems with this - just wanted to mention it.
I'm happy with the current situation as is. Only the additional data (repo
uuid/root url) would help, even if there are multiple uuids/root urls saved
there. Maybe store that as a list/hash.
was (Author: steveking):
{noformat:nopanel=true}
It's definitely better to have a different realm for every repository: users
should know/be told what they are entering their auth data for.
But users have had problems with this - just wanted to mention it.
I'm happy with the current situation as is. Only the additional data (repo
uuid/root url) would help, even if there are multiple uuids/root urls saved
there. Maybe store that as a list/hash.
{noformat}
> add repository root url and uuid to saved auth data
> ---------------------------------------------------
>
> Key: SVN-3926
> URL: https://issues.apache.org/jira/browse/SVN-3926
> Project: Subversion
> Issue Type: Improvement
> Components: libsvn_subr
> Affects Versions: trunk
> Reporter: Stefan Küng
> Fix For: 1.10-consider
>
>
> First reported here:
> http://svn.haxx.se/dev/archive-2011-02/0864.shtml
> Filing an issue so this won't get lost:
> Currently if the user want to have the auth data saved, it is saved in
> subversion\auth\svn.simple (or another subfolder). But it is saved with the
> auth realm string. Of course that's the right way to do it, but I would like
> to have other info saved as well, like the repo root url and/or the
> repository uuid. And then some APIs that allow me to list the saved auth
> data, delete a specific file, retrieve the login username (not the password,
> for obvious reasons).
> Use cases: users often want to login with a different username for a
> repository because they're using someone elses workstation/laptop for a day
> or two or they use a shared workstation but still want each commit assigned
> to the correct user (ugly, but happens more often than you might think).
> Right now there's no way to find out which saved auth file
> corresponds to a specific repository. So either users have to delete all the
> saved auth data for all repositories, or open each file in a text editor and
> then guess from the realm string which is the right file. If the repo root
> url was saved as well, I could do this in TSVN and show the user a list of
> repositories and have him chose the one to clear the auth data for.
> Another use case: retrieving the saved username would be useful for e.g. the
> integration with issue trackers. Usually the username is the same for the
> repository and the issue tracker (most setups work that way). Currently
> there's no way to filter the list of issues by username automatically for the
> issue tracker plugins because a username is not available. Using the repo
> root url or repo uuid which can be read from a working copy, I could then
> read out the saved username and provide that to the issue tracker plugins so
> they can filter for this username by default and reduce the list of open
> issues to that user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
