> On 11 Jul 2019, at 02:42, Mark Reynolds wrote:
>
> What platform are you on? What version of 389-ds-base? Please provide more
> information when asking questions on the mailing list otherwise most people
> will not respond to your questions - just an FYI.
>
>
>
> Since I am somewhat
> On 11 Jul 2019, at 04:31, Matt Shields wrote:
>
> We're looking at migrating our Solarwinds Serv-U users into 389-ds. We can
> export the user's password hashes which use the following format.
>
> - user password = mytestpass
> - pick two alpha salt (i.e. Bq)
> - new user password =
We're looking at migrating our Solarwinds Serv-U users into 389-ds. We can
export the user's password hashes which use the following format.
- user password = mytestpass
- pick two alpha salt (i.e. Bq)
- new user password = prepend the salt to the user's password (i.e.
Bqmytestpass)
- MD5 new
What platform are you on? What version of 389-ds-base? Please provide
more information when asking questions on the mailing list otherwise
most people will not respond to your questions - just an FYI.
Since I am somewhat familiar with the issue I will provide more
background information
When attempting to start 389 I get the following error.
[root@ openldap]# systemctl status dirsrv@slapd.service
● dirsrv@slapd.service - 389 Directory Server slapd.
Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor
preset: disabled)
Active: failed (Result: resources)
