[Java-SDK] Initialisierung scheitert durch fehlende Zertifikate (14/15) in certificate-config.yaml

Bug Classification

  • Affects multiple customers
  • Affects only one customer

Customer Interaction

  • Yes, reviewed together with the customer via TeamViewer
  • Yes, documented via screenshots
  • No, meeting is still pending
  • No interaction yet

Description of the Bug

SenderExample (und Client‑Initialisierung) schlägt fehl, weil certificate-config.yaml auf nicht mehr vorhandene Zertifikate verweist.

  1. SDK (Version 3.1.2) auschecken
  2. SenderExample starten
  3. Initialisierung bricht ab

Current behavior:

Exception in thread "main" FitConnectInitialisationException: Failed loading resource /trusted-root-certificates/PCA-1-Verwaltung-14.pem

Expected behavior:

Initialisierung lädt nur existierende Root‑Zertifikate und SenderExample startet ohne Exception.

Environments:

Additional Information:

client/src/main/resources/certificate-config.yaml enthält noch PCA-1-Verwaltung-14.pem und PCA-1-Verwaltung-15.pem, die im Repository nicht mehr vorhanden sind.

Dependency / relationship to other issues:

Responsible person / team:

Transfer history to different teams

Contact persons including contact details:

Screenshots / Logs / Requests:

Checklist:

  • Add Severity label
  • Add team label
  • Related/affected issues/stories/epics linked and explained in the bug issue
  • Creation of an automated test
  • Bugfix deployed on DEV
  • Bugfix tested on DEV
  • Bugfix deployed on TEST
  • Bugfix tested on TEST (possibly also by the connection project itself)
  • Successful fix reported to Team Operations (Teams channel)
  • Bugfix deployed on STAGE
  • Bugfix tested on STAGE if necessary
  • Bugfix deployed on PROD
  • Bugfix tested on PROD (possibly also by the connection project itself)
  • Final communication by Team Operations if necessary
  • Internal documentation was checked and updated if necessary
  • External documentation has been checked and updated if necessary
  • Updated changelog if necessary

Approach/Solution:

certificate-config.yaml aktualisieren, so dass nur existierende Zertifikate referenziert werden (z. B. 17/20/23/26).

Release version of the artifact: