Hi Fernando,
On 8/22/19 5:21 AM, Fernando Fuentes wrote:
Is there a how to for this procedure?
## Convert to PKCS#12:
# openssl pkcs12 -export -out demo.p12 -inkey
pki/private/demo.example.com.key -in pki/issued/demo.example.com.crt
Enter pass phrase for pki/private/demo.example.com.key:
I caught my mistake and corrected but now I get:
[root@hypersouth SSL]# pk12util -i hypersouth-net.p12 -d
/etc/dirsrv/slapd-hypersouth/ -W password
Enter Password or Pin for "NSS Certificate DB":
pk12util: PKCS12 decode not verified: SEC_ERROR_BAD_PASSWORD: The
security password entered is
Marc,
Thank you!
I will report back soon.
Regards,
Fernando Fuentes
Supervisor & Senior Systems Administrator
Email: ffuen...@aasteel.com
American Alloy Steel, Inc.
Houston, Texas
Website: http://www.aasteel.com
Phone: 713-744-4222
Fax: 713-300-5688
On 8/22/19 2:31 AM, Marc Muehlfeld
Marc,
Here is what I get:
[root@hypersouth SSL]# pk12util -i hypersouth-net.p12
/etc/dirsrv/slapd-hypersouth/ -W password
pk12util: function failed: SEC_ERROR_LEGACY_DATABASE: The
certificate/key database is in an old, unsupported format.
[root@hypersouth SSL]#
Regards,
Fernando Fuentes
So I finally got it to take by doing the following:
[root@hypersouth ~]# openssl pkcs12 -export -out hypersouth-net.p12
-inkey /etc/pki/tls/private/hypersouth_auth-2019.key -in
/etc/pki/tls/certs/hypersouth.aasteel.net.pem -certfile
/etc/pki/ca-trust/source/anchors/RapidSSLCA.crt
Enter pass
> On 21 Aug 2019, at 22:10, DaV wrote:
>
> Hi guys,
> Just update for this issue.
>
> Finally, I create multi windows sync agreement for each OU to sync the user
> account.
> like this:
>
>> DS Host: 389ds:389
>> Windows Host: dc01.example.com:389
>> DS Subtree:
Hi all,
First of all, I don't know whether if this is a bug and I don't know where to
submit a bug.
My 389ds info:
OS: CentOS Linux release 7.6.1810 (Core)
389ds: 389-ds-base-1.3.8.4-15.el7.x86_64
On 389ds server, I have configured like this
> # auto.master, service, example.com
> dn:
After getting everything working I was able to enable SSL on the console.
But now the console is unable to start with the error:
[Thu Aug 22 15:15:35.680397 2019] [:error] [pid 25091:tid
139708987033728] Password for slot internal is incorrect.
[Thu Aug 22 15:15:35.680824 2019] [:error] [pid
> On 23 Aug 2019, at 10:39, DaV wrote:
>
> Hi all,
> First of all, I don't know whether if this is a bug and I don't know where to
> submit a bug.
Let's do some investigation here first, but then I'd advise the RH bugzilla if
we determine what the cause is.
>
> My 389ds info:
> OS:
Hi William,
Thanks for your reply.
Sorry for incorrect message yesterday.
My windows sync agreement exactly is:
agreement1:
>> DS Host: 389ds:389
> >> Windows Host: dc01.example.com:389
> >> DS Subtree: ou=Users,dc=example,dc=com
> >> Windows Subtree: ou=ou1,OU=Accounts, DC=example,DC=com
> >>
Hi William,
> So, where did you read the docs on the setup? Maybe the docs are incomplete?
We are using Sun directory Server version 7, the configure on 389ds copied from
Sun Directory Server for the automount part.
> Can you correctly do a "ldapsearch" or "ldapwhoami" with -H
>
> On 23 Aug 2019, at 11:03, DaV wrote:
>
> Hi William,
>
>> So, where did you read the docs on the setup? Maybe the docs are incomplete?
> We are using Sun directory Server version 7, the configure on 389ds copied
> from Sun Directory Server for the automount part.
>
>> Can you correctly
NSS which stores the certificates requires a password for it's database. If you
look in /etc/dirsrv/admin-serv you'll see files like:
secmod.db
key3.db
key4.db
cert8.db
cert9.db
pkcs11.txt
These are the NSS database files. They store their material encrypted, which is
why a password is
13 matches
Mail list logo
