Add fixed DN field to Provision-to-LDAP mappings

Created on 19 November 2017, over 6 years ago
Updated 7 November 2023, 8 months ago

As reported in #1994242: Drupal to LDAP sync not happening.. → users have issues when configuring a valid mapping to LDAP. While we cannot fully anticipate a valid mapping configuration for their environment (e.g. what the valid objectClass attributes are needed), there should be no situation where the DN is not required.

One solution would be to provide one extra mapping up-front as a required field which the user would have fill out. Alternatively, but more obscure, would be deriving the DN from user data tables after an initial provisioning event.

✨ Feature request
Status

Closed: won't fix

Version

4.0

Component

Code

Created by

🇨🇭Switzerland grahl Zürich

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024