There would definitely be value in being able to determine "svn whoami"
in many scenarios. But AFAICT it would have to be "svn who-would-i-be"
because the actual credentials used depend on more than the cached
credentials, and can't be definitively determined without a roundtrip to
the server.
Case in point: on upgrading to Subversion 1.3.x, until we turned off
NTLM authentication, Subversion's use of the new version Neon caused the
client's username from the Windows session to be used, regardless of
what's in the credential cache. But if NTLM authentication failed, then
presumably the credential cache would be used. BTW, the --username
option did not override Neon's use of the session's username. Complex.
We had to use a packet sniffer to figure out what credentials were
actually being passed.
If you just want to know whose credentials are cached, you can construct
a small utility to parse the cache, it is text and that wouldn't be
difficult.
I'm only saying that that is not the complete story for all the ways
Subversion can be hosted and configured. Caveat emptor.
Stuart Celarier | Corillian Corporation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 4 15:38:48 2006