Class Fido2TrustController
Read-only: these endpoints surface configuration and metadata state that already exists in the server, so an administrator can see why enrollments are failing instead of that appearing to end users as a generic registration failure. Nothing here changes attestation behaviour, triggers a metadata download, or touches the document store.
SECURITY NOTE: as with the metrics endpoints, authentication and authorization are expected to be enforced at the infrastructure level (API gateway, OAuth interceptor, or reverse proxy) or via the Config API fido2 plugin, which applies the fido2 configuration scopes.
- Author:
- Janssen Project
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionjakarta.ws.rs.core.ResponseEffective attestation configuration: the mode in force, whether unattested authenticators are still accepted, and whether the trust anchors attestation depends on are present.jakarta.ws.rs.core.ResponseMDS health: loaded entry count, blob validity, and the outcome of the last refresh.
-
Constructor Details
-
Fido2TrustController
public Fido2TrustController()
-
-
Method Details
-
getAttestationConfig
@GET @Path("/attestation/config") @Produces("application/json") public jakarta.ws.rs.core.Response getAttestationConfig()Effective attestation configuration: the mode in force, whether unattested authenticators are still accepted, and whether the trust anchors attestation depends on are present.- Returns:
- attestation trust configuration
-
getMdsHealth
@GET @Path("/mds/health") @Produces("application/json") public jakarta.ws.rs.core.Response getMdsHealth()MDS health: loaded entry count, blob validity, and the outcome of the last refresh.Answers 503 when the status is DOWN, so the endpoint can be wired straight to a monitor. A metadata service switched off by configuration is reported as DISABLED with HTTP 200 — that is a deliberate choice, not an outage.
- Returns:
- MDS health status
-