On 23-Jul-05, at 6:08 AM, Gerhard Killesreiter wrote:
On Sat, 23 Jul 2005, Bèr Kessels wrote:
Op dinsdag 19 juli 2005 07:33, schreef Boris Mann:
On 18-Jul-05, at 11:22 AM, Bèr Kessels wrote:
For a more advanced webdav/svn system I am looking at a very simple mod_auth_mysql configuration, or even a mod_auth_mysql.module that module would include a permission "has apache access" or so. then the mod_auth_mysql will use such a scheme that it includes only Drupal users with that permission.
But before we are that far, I need to know how to get mod_auth_mysql to atuhtenticate against the druapl DB.
I had done some investigation into mod_auth_mysql. IIRC the result was that I should rather use somethign that is called mod_auth_forms (or similar). mod_auth_mysql will require you to use the ugly httpauth popup windows for authentification.
Regardless of "ugliness", there are two benefits to those pop-ups (and in general, Basic Auth schemes): 1. Well supported by browsers/operating systems -- e.g., even if an app doesn't directly support the entry of a user/pass, you can usually do http://user:pass@domain.com 2. Users can "save password" (really just a side effect of #1) -- which is what I've found really enjoyable with securesite I'm looking forward to more integration with other systems, especially those that extend on to the desktop. I'm looking at some bugs with this, but securesite + some node_access like OG + event (for example) == private iCal on your desktop. The trick of course being that you need to access Drupal over HTTP but also authenticate so you get the private nodes that are available to you. -- Boris Mann http://www.bmannconsulting.com