how does content profile integration work?
mtndan - January 27, 2009 - 15:48
| Project: | LDAP provisioning |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi, I have a batch of users I need to import. I see references to content profile module in your code, but I'm not sure how to accomplish the following:
1. ldap authentication - i have this working currently with ldap_integration module
2. map ldap data fields to content profile fields?
3. import users, and have their data populated from ldap into the content profile fields?
Please advise. Thanks!
#1
ldapdata module does not support content profiles. so you cannot sync content profile with the ldap data.
However, ldap_provisioning does support content profiles, that means that content profile fields can be exposed on the registration form, also they can be filled in in the csv file, which can then be uploaded to the ldap_provisioning and corresponding users created in drupal and ldap with their content profiles autocreated and content profile fields populated.
#2
Thanks for the reply.
After the content profiles are imported, will they be updated automatically if the LDAP data changes?
#3
No, ldapdata is not integrated with content profiles.
#4
This also doesn't seem obvious to me: how do I map more fields other than just first and last name to an LDAP entry with the Content Profile integration?
(For example, I'd like to create a field in the registration form for "Organization" that maps to an LDAP field "o".)
#5
No, you cannot do that with a current code. There is no ldapdata (drupal profile sync with the ldap account) equivalent for the content profile.
What current code does, it allows to use first and last names from the content profile registration form to build a ldap DN and be used in ldap entry.
#6
From Readme.txt it stated this ...
ldapdata.module depends upon the profile and ldapauth module and extends the
functionality to enable mapping of other LDAP attributes to Drupal attributes.
Also allows management of ldap attributes via the Drupal profile module.
Would there be any plan to use content_profile in conjunction with/replacement of profile module for mapping LDAP attributes?
From comment #1, #5 are you suggesting that ldap_provisioning can be used for importing purpose only? no read/write access is permitted to ldap, therefore, LDAP entry will not be updated even if updated in Drupal?
Thank you for your clarification.