You are here

README.txt in Lightweight Directory Access Protocol (LDAP) 7.2

Vocubulary of LDAP Authorization and its Code

----------------------
"Consumer"
----------------------
The "consumer" or entity that authorization is being granted.

Examples:  Drupal role, Organic Group group

----------------------
"Consumer Type"
----------------------
Machine ID of a consumer.  This is used in naming conventionss.

Examples:  drupal_role, og_group

----------------------
"Consumer Module"
----------------------
The module that bridges ldap_authorization and the consumer.
It needs to (1) provide a class: LdapAuthorizationConsumer<consumer_type>
and (2) implement hook_ldap_authorization_consumer.

Examples:  ldap_authorization_drupal_role


----------------------
"Authorization ID" aka "Consumer ID"
----------------------
The id of an individual authorization such as a drupal role or organic group.

Examples:  "authenticated user", "admin" (for drupal roles)
Examples:  "knitters on skates", "vacationing programmers" (og group names for organic groups)


----------------------
"Consumer Configuration"
----------------------
Configuration of how a users ldap attributes will
determine a set of Consumer ids the user should be granted.
Represented by LdapAuthorizationConsumerConf and LdapAuthorizationConsumerConfAdmin classes
and managed at /admin/config/people/ldap/authorization.  Stored in ldap_authorization database table.

---------------------
LDAP Server Configuration
---------------------
Each Consumer Configuration will use a single ldap server configuration to bind
and query ldap.  The ldap server configuration is also used to map the drupal
username to an ldap user entry.


----------------------
LDAP Authorization data storage:
---------------------

Authorization data is stored in user->data array

such as:

$user->data = array(
  'ldap_authorizations' => array(
    'og_group' => array (
      '3-2' => array (
        'date_granted' => 1329105152,
      ),
      '2-3' => array (
        'date_granted' => 1329105152,
      ),
    ),
    'drupal_role' => array (
      '7' => array (
        'date_granted' => 1329105152,
      ),
      '5' => array (
        'date_granted' => 1329105152,
      ),
    ),
  );

File

ldap_authorization/README.txt
View source
  1. Vocubulary of LDAP Authorization and its Code
  2. ----------------------
  3. "Consumer"
  4. ----------------------
  5. The "consumer" or entity that authorization is being granted.
  6. Examples: Drupal role, Organic Group group
  7. ----------------------
  8. "Consumer Type"
  9. ----------------------
  10. Machine ID of a consumer. This is used in naming conventionss.
  11. Examples: drupal_role, og_group
  12. ----------------------
  13. "Consumer Module"
  14. ----------------------
  15. The module that bridges ldap_authorization and the consumer.
  16. It needs to (1) provide a class: LdapAuthorizationConsumer
  17. and (2) implement hook_ldap_authorization_consumer.
  18. Examples: ldap_authorization_drupal_role
  19. ----------------------
  20. "Authorization ID" aka "Consumer ID"
  21. ----------------------
  22. The id of an individual authorization such as a drupal role or organic group.
  23. Examples: "authenticated user", "admin" (for drupal roles)
  24. Examples: "knitters on skates", "vacationing programmers" (og group names for organic groups)
  25. ----------------------
  26. "Consumer Configuration"
  27. ----------------------
  28. Configuration of how a users ldap attributes will
  29. determine a set of Consumer ids the user should be granted.
  30. Represented by LdapAuthorizationConsumerConf and LdapAuthorizationConsumerConfAdmin classes
  31. and managed at /admin/config/people/ldap/authorization. Stored in ldap_authorization database table.
  32. ---------------------
  33. LDAP Server Configuration
  34. ---------------------
  35. Each Consumer Configuration will use a single ldap server configuration to bind
  36. and query ldap. The ldap server configuration is also used to map the drupal
  37. username to an ldap user entry.
  38. ----------------------
  39. LDAP Authorization data storage:
  40. ---------------------
  41. Authorization data is stored in user->data array
  42. such as:
  43. $user->data = array(
  44. 'ldap_authorizations' => array(
  45. 'og_group' => array (
  46. '3-2' => array (
  47. 'date_granted' => 1329105152,
  48. ),
  49. '2-3' => array (
  50. 'date_granted' => 1329105152,
  51. ),
  52. ),
  53. 'drupal_role' => array (
  54. '7' => array (
  55. 'date_granted' => 1329105152,
  56. ),
  57. '5' => array (
  58. 'date_granted' => 1329105152,
  59. ),
  60. ),
  61. );