On Tue, Feb 07, 2012 at 08:52:24AM +0100, Ulrich Eckhardt wrote: > Am 03.02.2012 12:02, schrieb Frank Jaworski: > >Hello. We have our subversion repositories linked to a RADIUS server via > >https. When we access our repository via various SVN clients (TortoiseSVN, > >CollabNet, etc...), instead of one authentication per session, there is one > >authentication per action. > > According to what I remember from a recent thread here (couldn't > locate it any more, sorry, but it was ~2..3 weeks ago), this is > normal behaviour. What you perceive as a "session" just isn't, since > each operation makes one HTTP request on a separate TCP connection > and thus requires separate authentication.
Not sure what Frank means when he says "action". If one action is an update, a commit, and so on, then yes, this is how Subversion normally works. However it is possible to configure single sign-on with Apache modules such as mod_auth_kerb which makes authentication mostly transparent to users. If you are being asked to authenticate multiple times during the same operation (such as during one "update"), enabling KeepAlive and setting a high KeepAliveTimeout in the apache httpd config should help. This option allows Subversion clients to issue multiple requests over a single TCP connection. httpd.apache.org/docs/current/mod/core.html#kee
