Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.
Commentaire: Published by Scroll Versions from space DA and version BM-3.5

...

Sv translation
languageen


Introduction

BlueMind allows you to import users or groups from an LDAP directory (e.g. OpenLDAP). LDAP imports are incremental (new entries are added, and changes to data are recorded). Set up and execution of LDAP imports are domain-specific.

Imported user passwords are then validated against the LDAP server.

New users can connect to BlueMind even if their information has not been imported yet. Their BlueMind account will be created in the process if authentication is successful.

BlueMind users and groups are populated from the LDAP directory:

  • during installation and set up, through the initial import
  • regularly and automatically through scheduled jobs
  • on the spot, when an unknown user logs in.
Info

LDAP synchronization is designed based on a directory schema of the InetOrgPerson type .

Volet
borderWidth3

On this page:

Sommaire
maxLevel2

Related:

Installation

To access LDAP synchronization functionalities, you must install the plugin "ldap-import".

To do this, log into the server and use the following command to start installation:

Bloc de code
languagebash
titleDebian/Ubuntu
sudo aptitupde update
sudo aptitude install bm-plugin-admin-console-ldap-import bm-plugin-core-ldap-import
Bloc de code
languagebash
titleRedHat/CentOS
yum update
yum install bm-plugin-admin-console-ldap-import bm-plugin-core-ldap-import

Once installation is complete, restart the "bm-core" component using the following command:

Bloc de code
languagebash
bmctl restart

Set up

Only the global administrator is able to configure LDAP synchronization for a domain. Domain administrators are able to view settings and launch import jobs.

  • Log in as global administrator admin0@global.virt
  • Go to System Management > Modify Domains and select the domain you want to set up
  • Go to the "Directories" tab

FieldNote
LDAP server name or IP address

LDAP server IP address or FQDN.

Syntax:

  • hostname: connect to the LDAP server using an unencrypted connection on port 389
  • ssl:hostname: connect to the LDAP server using an SSL connection on port 636
  • tls:hostname: connect to the LDAP server using a TLS connection on port 389
Protocol

Choose which protocol to use:

  • PLAIN
  • TLS
  • TLS/accept all certificates
  • SSL
  • SSL/accept all certificates
Root directorySpecify the LDAP root directory
User DNDN of the root user used to connect to the LDAP server
PasswordThe user password used to connect to the LDAP server
LDAP filter for usersOnly users validated by this filter will be imported into BlueMind
LDAP filter for groupsOnly users validated by this filter will be imported into BlueMind
External IDAttribute of an invariant and unique LDAP entry identifier used to bind an LDAP entry to a BlueMind entry.
Split domain group

This field can be left empty.

It will be ignored if the split domain functionality is not configured for BlueMind.

Emails sent to members of this group will be redirected to another mail server in the same domain (through split domain configuration).

LDAP-BlueMind mapping

User attributes

BlueMindLDAP AttributeNote
loginuid

Values are mapped on import for compatibility reasons:

  • accented letters are replaced by their non-accented equivalent
  • all letters are changed to lowercase
  • spaces are replaced by

Un mapping (remplacement de caractères) est réalisé lors de l'import pour des raisons de compatibilité :

  • remplacement des lettre accentuées par la lettre non accentuée correspondante
  • passage en minuscule
  • remplacement des espaces par des
    • '_'
    firstnamegivenName
    lastnamesn
    descriptiondescription
    mail

    mail

    mailLocalAddress

    mailAlternateAddress

    gosaMailAlternateAddress

    BlueMind's default email address is defined from the first LDAP attribute of the following: "mail", "mailLocalAddress", "mailAlternateAddress", or "gosaMailAlternateAddress".

    The others will be used as alias email addresses.

    user mail quota

    mailQuotaSize

    mailQuota

    Must be expressed in bytes in LDAP.

    The first of these LDAP attributes to be found is used.

    work phonestelephoneNumber
    home phoneshomePhone
    mobile phonesmobile
    faxfacsimileTelephoneNumber
    pagerpager
    memberOfmemberOfList of groups the user is a member of. BlueMind users can only be added to LDAP groups imported previously.
    photoID jpegPhotoProfile picture: attribute content is imported as profile picture for related account 

    Group attributes

    BlueMindAttribut LDAPNote
    namecn
    descriptiondescription
    mailmail
    membermemberUidOnly users and groups already imported into BlueMind will be added to the group

    Role assignment

    From BlueMind 3.5, access to applications goes through is subject to the roles that users are assigned to users. As LDAP imports do not handle roles, no roles imported users are assigned to users when not assigned any roles and they are imported and users are unable to access applications (webmail, contacts, calendar).

    The easiest and most effective way of handling this is through groups:

    • in LDAP, assign one (or several, if desired) common group to users
    • launch an initial a first import: the group(s) are imported into BlueMind along with the users
    • go to the admin section and assign the desired roles to the group(s)
    Info

    Roles are maintained during subsequent imports and updates.

    In the future, simply ascribe assign new users to those groups this/ese group(s) in order to assign give them the desired roles.

    Astuce
    titleEditing Roles

    As new versions are released, new roles and improvements to features are regularly added to BlueMind.

    E.g. BlueMind version 3.5.9 allows administrators to enable or disable the ability for BlueMind users to connect to Thunderbird through new roles. In earlier versions, all users had this ability.

    To make sure that after the update the new right will be enabled for existing users, you must set the group(s) in which LDAP users have been ascribed to are as default groups.

    To do this, go to the group(s)' admin page, check the "Default group" box and save: