You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 26, 2024. It is now read-only.
I try to sync Mirakel against a taskd 1.1 setup. I'm not using self-signed certificates, but Class 3 certificates issued by the community certification authority CAcert. They use an immediate certificate in-between:
Root (CAcert Class 1) -> Intermediate (CAcert Class 3) -> taskd certificate, user certificates
When trying to import the configuration file created following the user guide, I receive following error message: "Die Konfigurationsdatei ist fehlerhaft" (translated back to English something like "The configuration file is broken"), it seems that Mirakel doesn't accept certificate chains.
The text was updated successfully, but these errors were encountered:
jenserat said:
Although I updated to 2.8, the problem still persists. Now taskd shows a message "Synchronisation abgeschlossen", "Schreibar hast Du eine fehlerhafte Konfigurationsdatei verwendet" (Schreibar should probably be Scheinbar?).
Debug logging in taskd does not show any connection attempt from Mirakel.
I attached an example configuration with the sensitive stuff removed.
Original Reporter: jenserat
Environment: Not Specified
Version: 2.7.*
Migrated From: https://mirakel.atlassian.net/browse/MIR-551
I try to sync Mirakel against a taskd 1.1 setup. I'm not using self-signed certificates, but Class 3 certificates issued by the community certification authority CAcert. They use an immediate certificate in-between:
Root (CAcert Class 1) -> Intermediate (CAcert Class 3) -> taskd certificate, user certificates
When trying to import the configuration file created following the user guide, I receive following error message: "Die Konfigurationsdatei ist fehlerhaft" (translated back to English something like "The configuration file is broken"), it seems that Mirakel doesn't accept certificate chains.
The text was updated successfully, but these errors were encountered: