RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
nsslapd-minssf valid value range is not clear

Version-Release number of selected component (if applicable):
389-ds-base-1.4.0.19-1.module+el8+1+a8d5e036.x86_64

How reproducible:
Always

Steps to Reproduce:
In Admin Guide, It is written - "The default nsslapd-minssf attribute value is 0, which means there is no minimum SSF for server connections. The value can be set to any reasonable positive integer. The value represents the required key strength for any secure connection."

But - 
[root@server /]# dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-minssf=130
Enter password for cn=Directory Manager on ldap://server.example.com: 
Error: {'desc': 'Server is unwilling to perform', 'info': 'Minimum SSF not met.'}

[root@server /]# dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-minssf=0
Enter password for cn=Directory Manager on ldap://server.example.com: 
Error: {'desc': 'Server is unwilling to perform', 'info': 'Minimum SSF not met.'}



Expected results:
Valid value range should be defined for the attribute.

The error message is irrelevant to the minssf settings, it points that LDAPS should be used instead of LDAP.
Closing as not a bug.