Hmmm, I've broken pysvn/svnpcpp somewhere in supporting may_save. I cannot
save credentials at all now... I'll debug the save logic and test the use
cases to find out how may_save and the config file options work together.
Barry
At 21-01-2004 23:16, you wrote:
>At 21-01-2004 13:42, Tobias Ringstrom wrote:
>Let me check I understand.
>>>The may_save means that there is no provider capable of saving the
>>>credentials.
>>>However in the case of the svncpp library I will always see may_save as
>>>true as it adds the file providers. Hence I could remove the may_save
>>>flag for the API and simplify the C++ and pysvn API.
>>>I'm guessing you are going to say I have this wrong :-)
>>
>>I'm afraid I have to. It is possible to globally disable saving of
>>authentication credentials by setting store-auth-creds to "no" in the
>>config file. The command line client also has an option --no-auth-cache
>>which does the same thing. The may_save that is passed to the prompt
>>function is set to FALSE if any of these options are used.
>
>With a well designed GUI the store-auth-creds in the config file is not
>required.
>I can see I'll end up with a FAQ pointing out the problems that
>store-auth-creds
>cause a GUI client.
>
>I have this in my config:
>
>[auth]
>store-password = no
>store-auth-creds = no
>
>and may_save is passed in as 1 when I access a repo via HTTP:
>that needs a username/password. But as you say the creds are not
>stored when I set may_save to 1 in the creds struct.
>
>Being passed 1 for may_save in the case is a bug with svn auth?
>
>Barry
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@rapidsvn.tigris.org
>For additional commands, e-mail: dev-help@rapidsvn.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 22 01:05:33 2004