Re: Feature Request: Allow "save authentication" for reading and writing separately

Bruce Gough wrote:
>
>
> Stefan Küng wrote:
>> Bruce Gough wrote:
>>> Feature Request: Allow "save authentication" for reading and writing
>>> separately
>>>
>>> I have been using tortoiseSVN for a couple of years, and it works
>>> great. To avoid mistakes, I leave my client configured so that I must
>>> authenticate every time I access the repository. I have avoided doing
>>> "update" or completing the commit dialog by mistake more than once.
>>>
>>> My only problem with this is when I am doing activities like "check
>>> for modifications", then I click "Check repository", it does an
>>> authentication step. Then if I want to double click any file in the
>>> list of changed files and see the differences, it does another
>>> authentication each time I double click another file in the list of
>>> changed files.. Each one has the "save authentication" checkbox, but
>>> I think that checking it would save the authentication and use it for
>>> all authentication steps.
>>>
>>> I have worked around this by checking the box, then later going into
>>> the settings and setting it back to requesting authentication.
>>>
>>> It might be a bug for the specific case where I have checked for
>>> modifications, then must authenticate for each file on which I want
>>> to view the differences. It seems like it should not be necessary then.
>>>
>>> One possible way to improve this could be to have a separate flag for
>>> "read" type operations vs. "write" type operations. Even though the
>>> diff of modifications could allow writing a merged file, that would
>>> not update the repository so it would count as a read operation.
>>
>> That feature is already implemented :)
>> You have to configure your server accordingly.
>>
>> Either configure the 'read' operations to not require authentication
>> at all (anonymous access) and only require authentication for the
>> write operations, or you could set up two different users, one which
>> has only read access (but still needs to authenticate, and for which
>> you then store/save the authentication data), and another one with
>> write access (for which you won't store/save the authentication data).
>>
>> Stefan
>>
>>
> Thank you for responding.
>
> We use collabnet authentication with subversion, and are at about 6
> developers. Doubling the users would come close to the license limit. My
> admin does not like the idea of anonymous access. It sounds like the
> saved authentication would fail, then it would come back with the prompt.

Why doubling? Just set up one user who has read access (e.g.
'developerread'). And each of you has a separate account for write
access (which of course you should not save the authentication for).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org