Provisioning and LDAP
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Hi,
automatic provisioning does not work with LDAP, as %USERID% fetches the UID, which is usually a UUID Value and completly senseless for Email, instead with LDAP we need the DisplayName (which is the real user login Name).
so please add the patch below to make also a %DISPLAYNAME% parameter available.
*** Config.php.orig 2020-01-27 22:04:10.591445448 +0100
--- Config.php 2020-01-27 22:05:04.002460570 +0100
***************
*** 112,118 ****
}
/**
! * Replace %USERID% and %EMAIL% to allow special configurations
*
* @param string $original
* @param IUser $user
--- 112,118 ----
}
/**
! * Replace %USERID%, %DISPLAYNAME% and %EMAIL% to allow special configurations
*
* @param string $original
* @param IUser $user
***************
*** 122,127 ****
--- 122,130 ----
if ($user->getUID() !== null) {
$original = str_replace('%USERID%', $user->getUID(), $original);
}
+ if ($user->getDisplayName() !== null) {
+ $original = str_replace('%DISPLAYNAME%', $user->getDisplayName(), $original);
+ }
if ($user->getEMailAddress() !== null) {
$original = str_replace('%EMAIL%', $user->getEMailAddress(), $original);
}
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the parameter replacement method in Config.php and its existing %USERID% and %EMAIL% behavior. Add the requested %DISPLAYNAME% handling, update the nearby documentation comment, and verify that LDAP provisioning can use the new placeholder without changing existing substitutions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100