Depracated
Last updated on
30 April 2025
This is a summary of use cases where LDAP data is used to create, remove, or synch Drupal data (users, profile fields, roles, organic groups, etc.) based on LDAP data.
The columns are the means of provisioning... the how and when the synching should take place. The rows are the data affected.
Table Definitions: Means of Provisioning
- On User Logon. When a user authenticates to drupal
- Admin Interface. By administrator on individual basis
- Feeds. Automation or manually via Feeds Module
- Batch. Automated via LDAP Modules to perform batch actions triggered by cron
- API Functions and Hooks. Functions available to call from other modules or drush.
Table Definitions: Drupal Objects and Actions
- Create Drupal Account
- Associate Drupal Account with LDAP
- Remove Drupal Account
- Remove Drupal Association with Drupal account
- Populate Profile Data
- Populate User Fields
- Create Drupal Roles
- Remove Drupal Roles
- Assign and Remove Drupal Roles to Users
- Create Organic Groups
- Remove Organic Groups
- Assign and Remove Users from Organic Groups
- Create and Populate Drupal Nodes and Entities
| Task | On User Logon | Admin Interface | Feeds | Batch | API Functions |
|---|---|---|---|---|---|
| Create Drupal Account | Configured in LDAP Authentication | Built into Drupal | Use LDAP Feeds | Not Available | |
| Associate Drupal Account with LDAP | Configured in LDAP Authentication | Not Available | Use LDAP Feeds | Not Available | |
| Remove Drupal Account | Not Available | Built into Drupal | Not Available | Not Available | |
| Remove Drupal Association with Drupal account | Configured in LDAP Authentication. Requires mixed mode authentication enabled. | Not Available | Not Available | Not Available |
Help improve this page
Page status: Not set
You can:
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion
