The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Here's a patch with
- improvements concerning the email extraction stuff (I forgot a few things in my previous patch)
- Realname extraction, in case you wan't tour Drupal auto-created accounts to be named after the users's real names instead of their login (to allow that, $cas_user_register must be true, and $cas_authmap must be false).
Patch was made against the latest HEAD (1.1.17)
| Comment | File | Size | Author |
|---|---|---|---|
| cas.module_1.1.17.patch | 8.6 KB | deelight |
Comments
Comment #1
jdleonardThanks for this patch. My install of Eclipse didn't like it so I manually patched the file, but that's probably my fault (lack of knowledge of patches), not yours.
I am in a similar situation as aclight in this ldap integration issue. I am developing a new Drupal site for my university's student association and have read only access to an LDAP database (but I am not permitted to perform LDAP authentication). I have hacked the patched CAS module so that when users log in via CAS for the first time, their real name is pulled from LDAP and put in a profile field. What I need instead is for the user to be directed to a form after their first CAS login that has their real name pre-filled from LDAP that will set the realname profile field upon submission. I need to do this for FERPA reasons (if the user submits the pre-filled form field, they are voluntarily giving that information to my site). I am fairly new to Drupal and I'm not sure exactly how to accomplish this. Any advice would be most welcome!
Comment #2
jdleonardI just submitted a patch for the CAS module that allows an administrator to specify a page to which a user is redirected upon their first (initial) login with CAS: http://drupal.org/node/144378
Comment #3
metzlerd commentedThis seems like its getting out of hand.... More and more LDAP features are starting to creep into CAS, and it doesn't feel right to me. I think we need a hook based approach to this problem. Another individual submitted a patch to make CAS invoke the login hook and that feels more right to me. Maybe we need to explore moving all this LDAP functionality into another module. There are many other ways (besides LDAP) to get user information. At my university we use web service calls, but you might be pulling these from a database.
All this LDAP stuff feels outside of the CAS spec. Thoughts?
Comment #4
deelight commentedI agree, I think all of this should be part of the LDAP Integration module. At the moment, it only allows LDAP information retrieval if users log in via LDAP, but it would certainly be a much cleaner way to do it.
Comment #5
metzlerd commentedMy understanding is that this is now possible with the ldap_data module, given the support for the login hook in drupal.
Dave