With Open LDAP, the SSHA password MUST have the prefix {SSHA} before the
password string, ex:
userpassword: {SSHA}sOO2ymlVcl5RtKZnCq8moWc25cvXpaTu
Which the decoded value already has. In the past, just using the value "as-is" from Oracle has worked for me, so not clear to me why they are hitting any issue.
mime-decode e1NTSEF9S3hNQVVoRGY0Y0ZMVXdVREZQb1VDMFNvRFdRb0c2TnNLRTVZUWc9PQ=
'{SSHA}KxMAUhDf4cFLUwUDFPoUC0SoDWQoG6NsKE5YQg=='
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>