Password Sync Service, and 389 Console do not work when a ECDSA Certificate is installed

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50160

• Created at 2019-01-15 06:14:36 by conathan
• Closed at 2020-02-26 16:49:30 as wontfix
• Assigned to mhonek (@kenoh)

---

Issue Description

Password Sync Service, and 389 Console do not work when a ECDSA Certificate is installed. Begins working when a RSA Certificate is installed (No compatible ciphers I suspect)

Package Version and Platform

389-Console-1.1.15-x86_64.msi, (on windows 10)
389-PassSync-1.1.7-x86_64.msi, (on windows 10)
389-admin-1.1.46-1, (on Centos 7.6, from EPEL)
389-ds-base 1.3.8.4-18 (on Centos 7.6, from EPEL

Steps to reproduce

1. Generate a ECDSA Certificate (My tests were using one from Comodo
2. Install into the /etc/dirsrv/admin-serv, (and/or slapd-NAME)
   3a. Attempt to connect using the 389 console ( 389-Console-1.1.15-x86_64.msi)
   3b. Attempt to use the PassSync service to update a password (389-PassSync-1.1.7-x86_64.msi)

Actual results

Unable to connect to server

Expected results

Connecting Normally to Server

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2019-01-15 06:19:16

I think the server currently doesn't support/present ECDSA certificates, which may be the source of this issue. You can see more here: #3069

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2019-01-15 06:19:17

Metadata Update from @Firstyear:

• Custom field component adjusted to None
• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-02-07 17:58:29

Metadata Update from @mreynolds389:

• Issue set to the milestone: 1.4.1

[389-ds-bot]

Comment from mhonek (@kenoh) at 2019-02-07 17:58:41

Metadata Update from @kenoh:

• Issue assigned to kenoh

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-02-26 16:49:32

Closing ticket since 380-console is EOL, and we have issue 50010 to track the other ECDSA work...

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-02-26 16:49:32

Metadata Update from @mreynolds389:

• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)