Project

General

Profile

Anomalie #2128

configuration des vcards ldap

Added by Emmanuel GARETTE (2) almost 10 years ago. Updated almost 10 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Category:
-
Start date:
09/29/2011
Due date:
% Done:

100%

Spent time:
Distribution:
EOLE 2.3

Description

Les vcards des utilisateurs sont vides. Il serait bien de les remplir automatiquement à partir des informations de l'annuaire.

Pour cela il faut remplacer :

  {mod_vcard, []},

par :

  {mod_vcard_ldap, [
    {ldap_base, "ou=cadoles,ou=education,o=gouv,c=fr"},
    {ldap_filter, "(objectClass=inetOrgPerson)"},
    {ldap_vcard_map,
    %% vcard patterns
     [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname
      {"GIVEN", "%s", ["givenName"]},
      {"FAMILY", "%s", ["sn"]},
      {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John" 
      {"EMAIL", "%s", ["mail"]},
      {"BDAY", "%s", ["birthDay"]},
      {"ORGNAME", "%s", ["o"]},
      {"ORGUNIT", "%s", ["ou"]},
      {"LOCALITY", "%s", ["l"]},
      {"STREET", "%s", ["Street"]},
      {"TEL", "%s", ["Phone"]}
     ]},
    %% Search form
    {ldap_search_fields,
     [{"User", "%u"},
      {"Name", "givenName"},
      {"Family Name", "sn"},
      {"Email", "mail"}]},
    %% vCard fields to be reported
    %% Note that JID is always returned with search results
    {ldap_search_reported,
     [{"Full Name", "FN"},
      {"Nickname", "NICKNAME"}]}
  ]},

Par contre, il faut vérifier la correspondance des différents champs, n'ayant pas de serveur Scribe.

Associated revisions

Revision 909ffae9 (diff)
Added by Joël Cuissinat almost 10 years ago

Ajout de la configuration des vcards ldap (fixes #2128)
  • tmpl/ejabberd.cfg : remplacement de mod_vcard par mod_vcard_ldap et sa configuration

History

#1 Updated by Joël Cuissinat almost 10 years ago

  • Status changed from Nouveau to Résolu
  • % Done changed from 0 to 100

#2 Updated by Joël Cuissinat almost 10 years ago

  • Assigned To set to Joël Cuissinat
  • Target version set to Mises à jour 2.3 - 03 RC
  • Distribution set to EOLE 2.3

à partir de "BDAY" (compris) les attributs ldap associés sont protégés par des acl donc en suivant la "politique de confidentialité générale", il y a peu de chance qu'on ait besoin de les remplir réellement ...

#3 Updated by Joël Cuissinat almost 10 years ago

  • Status changed from Résolu to Fermé

Also available in: Atom PDF