#50869 Setting nsslapd-allowed-sasl-mechanisms truncates the value
Closed: wontfix by spichugi. Opened by mreynolds.

Adding multiple mechanisms to nsslapd-allowed-sasl-mechanisms ignores all but one of the mechanisms specified

ldapmodify -D ...
dn: cn=config
changetype: modify
replace: nsslapd-allowed-sasl-mechanisms 
nsslapd-allowed-sasl-mechanisms: PLAIN LOGIN     
ldapsearch -D ...-b "cn=config" nsslapd-allowed-sasl-mechanisms=* nsslapd-allowed-sasl-mechanisms
dn: cn=config
nsslapd-allowed-sasl-mechanisms: LOGIN

What happens in ./dirsrvtests/tests/suites/gssapi/simple_gssapi_test.py? That seems to set these mechanisms ...

Perhaps this test or a similar test could be extended with the behaviour you're seeing.

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

Metadata Update from @mreynolds:
- Issue priority set to: critical

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1816854

Metadata Update from @spichugi:
- Issue assigned to spichugi

https://pagure.io/389-ds-base/pull-request/50997

fc95cf3ad..dd266dacc master -> origin/master
d74da7327..9a2beafce 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
aff1a2831..9c59d0095 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

Metadata Update from @spichugi:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3922

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata