#50160 Password Sync Service, and 389 Console do not work when a ECDSA Certificate is installed
Closed: wontfix 6 months ago by mreynolds. Opened 2 years ago by conathan.

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


I think the server currently doesn't support/present ECDSA certificates, which may be the source of this issue. You can see more here: https://pagure.io/389-ds-base/issue/50010

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

2 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

2 years ago

Metadata Update from @mhonek:
- Issue assigned to mhonek

2 years ago

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

Metadata Update from @mreynolds:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

6 months ago

Login to comment on this ticket.

Metadata