Bug 53448 - Whitelist EXTERNAL supportedSASLMechanisms in openldap
Whitelist EXTERNAL supportedSASLMechanisms in openldap
Status: VERIFIED WORKSFORME
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on: 43732
Blocks: 44164 53449
  Show dependency treegraph
 
Reported: 2021-06-15 16:30 CEST by Ferenc Géczi
Modified: 2024-01-03 17:48 CET (History)
6 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ferenc Géczi univentionstaff 2021-06-15 16:30:39 CEST
As long as notifier explicitly requests the EXTERNAL mechanism,
```
grep -n 'mechanism\[\]' src/notify.c
343:            const char mechanism[] = "EXTERNAL";
```
The EXTERNAL mechanism should be explicitly whitelisted in /etc/ldap/sasl2/slapd.conf.

Make sure that the EXTERNAL mechanism is available with the command below:

```
ldapsearch -LLLx -H ldapi:// -b '' -s base supportedSASLMechanisms | grep EXTERNAL
supportedSASLMechanisms: EXTERNAL
```
Comment 1 Philipp Hahn univentionstaff 2021-06-15 17:59:39 CEST
Our /etc/ldap/slapd.conf already conatins

> access to *
>     by sockname="PATH=/var/run/slapd/ldapi" write

which is enough for

> ldapsearch -Y EXTERNAL -H ldapi://

to work. So what's missing?

(In reply to Ferenc Géczi from comment #0)
> ldapsearch -LLLx -H ldapi:// -b '' -s base supportedSASLMechanisms | grep
> EXTERNAL
> supportedSASLMechanisms: EXTERNAL
> ```

It already does.
Comment 2 Florian Best univentionstaff 2024-01-03 17:48:28 CET
OK