RE: mod_dav_svn & X.509 certificate authorization
From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Fri, 21 Aug 2009 10:17:10 +0200
> Van: Udo Rader [mailto:listudo_at_bestsolution.at]
I don't know about the previous thread, and I'm not 100% sure, but I would think that this is pure Apache+SSL business, not Subversion's. I mean, shouldn't Apache be able to map the X.509 SSL client auth to a username, which is then passed on (like any normal auth mechanism)? Why would you need a second authentication step, just to get the username? Apache already knows who the user is, doesn't it?
I haven't done SSL client auth for a while, but I guess that there are a couple of ways to infer a username from a client certificate:
In an Apache+SVN scenario, Subversion really doesn't care how Apache authenticated the user, as long as Apache communicates the username to mod_dav_svn (like with any other auth mechanism).
>
I don't know, but I'm sure other SVN users have also had this question, and maybe some have come up with nice working solutions for this. So maybe someone else can comment on this...
Regards,
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.