We want to use Drupal on our intranet mainly for its forum capabilities. Since end users have already signed onto our network, I don't want them to have to login to our Drupal site again. I want Drupal to authenticate and recognize users based upon the login name found in the HTTP header. What I hope to acomplish is that a user can access our drupal site and post a forum topic without needing to supply a username and password. It sounds like Webserver_auth module is what we need to use is this correct?
If the Webserver_auth module it the correct module to use, is there any special setup we need to do to our webserver and/or dupal to get this working, Or is installing the module in Drupal all we need to do?
Comments
automatic login: Webserver_auth
I just stumbled on your post the other night while searching for "automatic login" and it is what led me to webserver_auth. Your post is almost a year old so I am not sure I am being any help there, but I wanted to go on record that webserver_auth worked a treat for me.
We run PubCookie (www.pubcookie.org) for intranet auth/auth and so have what we think is a trustworthy REMOTE_USER variable on our Apache server at all times. After setup I tested a couple of other accounts and Drupal accounts were created automatically as expected. I was able to then turn off login block. One gotcha: My original "admin" account was generic and not a PubCookie auth'd account. So I had to turn off webserver_auth and go back and promote my working PubCookie'd account to admin. Once webserver_auth is turned on, it didn't want to let me log off. "Always on" Cool.
I see in the TODO section: " - optionally grab elements from LDAP server (e.g. Windows Active Directory) immediately after user login. this will auto populate fields like phone number, birthday, etc."
This would be awesome. I have all my folks in an LDAP Directory (Fedora Directory Services) and it would be great to grab phone number, mailstop, full/display name (CN) and other bits and automatically add them to custom profile fields at the moment their Drupal accounts are created. This would seem to take some doing (another configuration/settings block?) to map (variable) LDAP attributes to (variable) custom profile fields. It would be great, though.
I have just been working with Drupal for a few months in pre-production mode but I have to say how much I like my choice. Compared to a few other CMS that I admired (but found too challenging) the way that things are laid out in Drupal (DB tables, modules) seems comparatively easy for amateurs like me to understand. Imagine, modules that are a single file!
Thanks!
Jim
ldapdata obviates Webserver_auth TODO?
I had installed the ldap_integration module, but I hadn't installed every piece. Now that I have installed/activated ldapdata.module, it looks like it pulls in custom profile fields and will let me map them to LDAP attributes. Cool!
Sooo, for anybody running Web auth system (like PubCookie) alongside their own LDAP server (or maybe a parent LDAP server) it looks like I don't have to populate profile values with anything at account creation time -- just use mapped LDAP attributes. This is going to be great. I need to browse the modules listing more often!
Off to look for some addressbook module that will allow folk to browse LDAP via Drupal.
Jim