User Tools

Site Tools


ldap_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ldap_integration [2019/07/25 12:49]
127.0.0.1 external edit
ldap_integration [2020/09/22 16:06] (current)
lucy [Troubleshoot problems]
Line 3: Line 3:
 LUCY has an LDAP API, which allows the administrator to: LUCY has an LDAP API, which allows the administrator to:
  
-  * import recipients  +  * import recipients and users directly from your directory service 
-  * import users (LUCY administrators)+  * authorize users in the Admin console, Enduser portal and Awareness website
  
-directly from your directory service.+==== Sync tool for Windows ==== 
 + 
 +Besides LDAP API, there is a tool that can be run on Windows machines to sync your Active Directory groups with Lucy, see more [[ldap_synchronization_tool|here]].
  
  
Line 70: Line 72:
  
 It is possible to configure LUCY autoupdate recipient list of from an LDAP Server. It is possible to configure LUCY autoupdate recipient list of from an LDAP Server.
-Note, this configuration will not be active if there are global settings for recipients import enabled.+ 
 +:!: Note, this configuration will not be active if there are global settings for recipients import disabled.
  
 {{ :autoupdate_recepients.png?600 |}} {{ :autoupdate_recepients.png?600 |}}
Line 103: Line 106:
   * 4.Phone - recipient phone number   * 4.Phone - recipient phone number
  
 +To configure other recipient fields to match Active Directory attributes go to the LDAP Fields Associations page (Settings > LDAP Settings > LDAP Fields Associations):
 +
 +{{ ::ldap_fields_associations.png?500 |}}
 +
 +:!: Recipient's custom fields are also supported.
 +
 +
 +===== Login Lucy through Active Directory (LDAP) =====
 +
 +Lucy allows users to login with their Active Directory account.
 +
 +=== Admin console & Enduser portal ===
 +
 +In order users to login Admin console or Enduser portal you should first import accounts to Lucy from your Active Directory. See [[ldap_integration#importing_users_via_ldap|this]] section for more details. \\
 +
 +:?: Please note that to login Lucy you should use an appropriate user role that can be configured within the LDAP Update Preferences page (Settings > LDAP Settings > LDAP Update Preferences). \\
 +
 +User roles used to access Admin console: **Administrator, View, User, Supervisor**. \\
 +User role used to access Enduser portal: **Enduser**. \\
 +
 +=== Awareness website ===
 +
 +Lucy has an option to send a non-unique link for awareness website, but it requires users to login with their AD account to access the website. It also requires endusers to be imported into Lucy (see previous section).
 +
 +To enable LDAP login for Awareness website, tick the option "**Enduser Direct login**" within the Base Settings in your campaign:
 +
 +{{ ::enduser_direct_login.png?400 |}}
 +
 +and the option "**Do not send emails**" within the Website section of the Awareness settings:
 +
 +{{ ::do_not_send_emails.png?500 |}}
 +
 +This enables the Global Link that can be used to access Awareness website after successful login via LDAP:
 +
 +{{ ::global_link.png?600 |}}
 +
 +The option "Do not send emails" disables sending awareness emails from campaign, that allows to share the Global Link through your own channel.
 +
 +===== Troubleshoot problems =====
  
 +  * An error occurs during the connection to Azure AD LDAPS: \\ \\ <code>Error connecting to LDAP Server: 80090308: LdapErr: DSID-0C090446, comment: AcceptSecurityContext error, data 52e, v2580</code> **Solution:** Invalid Login or Password. \\ Login must be in the format CN=<username>OU=<ou>, for example: CN=UserTest,OU=AADDC Users
 +  * An error occurs when logging in at /admin or /user using Azure AD account: **Invalid LDAP user login or password.** \\ \\ **Solution:** Please make sure you have enabled your NTLM password hash synchronization. Users cannot bind using secure LDAP or sign in to the managed domain, until you enable password hash synchronization to Azure AD Domain Services. Follow the instructions below, depending on the type of users in your Azure AD directory. Complete both sets of instructions if you have a mix of cloud-only and synced user accounts in your Azure AD directory. \\ \\ [[https://aka.ms/aadds-pwsynccloud|Instructions for cloud-only user accounts]] \\ [[https://aka.ms/aadds-pwsync|Instructions for synced user accounts]]
ldap_integration.1564051797.txt.gz · Last modified: 2019/07/25 12:49 by 127.0.0.1