Destinations können nicht aktiviert werden
Zusammenfassung
Destinations können nicht aktiviert werden.
Schritte zum Reproduzieren
- Neue Destination im Testing Self-Service-Portal anlegen
- Destination zum Bearbeiten aufrufen
- Status in
active
ändern - Speichern
- Status ist immer noch
created
An andere Änderungen werden nicht gespeichert.
Relevante Protokolle/Screenshots/Anfragen
Zustelldienst Log
2022-03-10 15:55:11.357 DEBUG 1 --- [nio-8080-exec-9] d.f.z.security.ZustelldienstPrincipal : Authenticated user '-internal-ssp-dest-f382c37b-7bd5-4e33-90d9-e3d737c624f6' with scopes: [manage:destination:f382c37b-7bd5-4e33-90d9-e3d737c624f6]
2022-03-10 15:55:11.359 INFO 1 --- [nio-8080-exec-9] d.f.z.controller.DestinationAPI : Fetching destination f382c37b-7bd5-4e33-90d9-e3d737c624f6
Hibernate: select destinatio0_.id as id1_4_, destinatio0_.callback_id as callback8_4_, destinatio0_.destination_id as destinat2_4_, destinatio0_.encryption_kid as encrypti3_4_, destinatio0_.metadata_versions as metadata4_4_, destinatio0_.reply_channels as reply_ch5_4_, destinatio0_.status as status6_4_, destinatio0_.status_since as status_s7_4_ from destination destinatio0_ where destinatio0_.destination_id=?
Hibernate: select contactinf0_.id as id1_3_0_, contactinf0_.address as address2_3_0_, contactinf0_.fk_destination_id as fk_desti7_3_0_, contactinf0_.email as email3_3_0_, contactinf0_.legal_name as legal_na4_3_0_, contactinf0_.phone as phone5_3_0_, contactinf0_.unit as unit6_3_0_ from contact_information contactinf0_ where contactinf0_.fk_destination_id=?
Hibernate: select destinatio0_.fk_destination as fk_desti3_5_0_, destinatio0_.id as id1_5_0_, destinatio0_.id as id1_5_1_, destinatio0_.fk_destination as fk_desti3_5_1_, destinatio0_.identifier as identifi2_5_1_ from destination_service destinatio0_ where destinatio0_.fk_destination=?
Hibernate: select submission0_.fk_destination_service as fk_desti4_11_0_, submission0_.id as id1_11_0_, submission0_.id as id1_11_1_, submission0_.fk_destination_service as fk_desti4_11_1_, submission0_.mime_type as mime_typ2_11_1_, submission0_.schema_uri as schema_u3_11_1_ from submission_schema submission0_ where submission0_.fk_destination_service=?
Hibernate: select regions0_.fk_destination_service as fk_desti1_6_0_, regions0_.region as region2_6_0_ from destination_service_regions regions0_ where regions0_.fk_destination_service=?
2022-03-10 15:55:11.439 DEBUG 1 --- [io-8080-exec-23] d.f.z.security.ZustelldienstPrincipal : Authenticated user '-internal-ssp-dest-f382c37b-7bd5-4e33-90d9-e3d737c624f6' with scopes: [manage:destination:f382c37b-7bd5-4e33-90d9-e3d737c624f6]
2022-03-10 15:55:11.440 WARN 1 --- [io-8080-exec-23] o.s.web.servlet.PageNotFound : No mapping for POST /v1/destinations/f382c37b-7bd5-4e33-90d9-e3d737c624f6/Qu4r9N2C7JVoHghL6-fhFCFz6UQ2ACj6K4rcdLWsuFE
2022-03-10 15:55:11.441 WARN 1 --- [io-8080-exec-23] o.z.problem.spring.common.AdviceTraits : Not Found: No handler found for POST /v1/destinations/f382c37b-7bd5-4e33-90d9-e3d737c624f6/Qu4r9N2C7JVoHghL6-fhFCFz6UQ2ACj6K4rcdLWsuFE
2022-03-10 15:55:11.666 DEBUG 1 --- [io-8080-exec-21] d.f.z.security.ZustelldienstPrincipal : Authenticated user '-internal-ssp-dest-f382c37b-7bd5-4e33-90d9-e3d737c624f6' with scopes: [manage:destination:f382c37b-7bd5-4e33-90d9-e3d737c624f6]
2022-03-10 15:55:11.668 INFO 1 --- [io-8080-exec-21] d.f.z.controller.DestinationAPI : Fetching destination f382c37b-7bd5-4e33-90d9-e3d737c624f6
Da wird anscheinend ein Pfad falsch zusammengebaut: POST /v1/destinations/f382c37b-7bd5-4e33-90d9-e3d737c624f6/Qu4r9N2C7JVoHghL6-fhFCFz6UQ2ACj6K4rcdLWsuFE
Da steckt die Key-ID drin, ich hatte aber den Schlüssel gar nicht aktualisiert.
Durchführungsplan
-
SSP Zustelldienst Api Nutzung anpassen (https://git.fitko.de/fit-connect/self-service-portal/-/merge_requests/37) -
Änderungen auf DEV ausrollen (https://git.fitko.de/fit-connect/infrastruktur/-/merge_requests/71) -
Changelog vorbereiten (docs!145 (merged))
Edited by Florian Kaufmann