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)
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
Unable to connect to server
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
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.1
Metadata Update from @mhonek: - Issue assigned to mhonek
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)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3219
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.