+38
−10
+34
−0
+59
−0
Loading
FM handed every partner a partnerStatusLink and had no route behind it, so a partner reporting a federation status change got a 404. Adds the callback router from ADR-0054 under /operatorplatform/federation/v1/callbacks/: it requires the fed-mgmt-notif scope, resolves azp to an active partner, and answers 404 unless the federationContextId is an outbound context of that caller. The onPartnerStatusEvent handler maps OPG.04's FederationStatus onto federation_contexts.status and is idempotent. Callbacks about zones or network codes are accepted and logged rather than rejected, since shared_resource_catalogues does not exist yet. PartnerAuthenticator now takes the required scope, defaulting to fed-mgmt, and the dev realm gains fed-mgmt-notif as an optional scope on each partner client. Without it FM's own callback client could not get a token either, so notifications had never worked against real Keycloak.