Package io.jans.fido2.service.readiness
package io.jans.fido2.service.readiness
-
ClassDescriptionProduces the
assetlinks.jsonandapple-app-site-associationfiles of a configured relying party, for the admin to deploy on the RP-ID host.Says whether a resolved address is one the readiness fetcher must never connect to.One readiness check: a stable id, a status and a short reason.Outcome of one readiness check.Compares a deployedassetlinks.json/apple-app-site-associationwith what the RP configuration says it should contain.The one definition of what a relying party's association files should contain, built from itsRequestedParty.The structured answer of the native app readiness endpoint.One check as it appears in the response:statusispass,warnorfail.Runs the native app readiness checks for one configured relying party: feature gate, lookup, RP ID validation, per-RP result cache, rate limits, then the reachability and content checks.The requested relying party is not configured.A rate limit refused the request;NativeReadinessService.RateLimited.retryAfterSeconds()says when to ask again.Decides whether a relying party's association files are reachable the way Android and iOS need them: answered with 200 by the RP ID host itself, with a JSON content type, within the size and time limits.Reachability checks for one association file, together with the fetch they were derived from.Bounds how much outbound work the readiness endpoint can cause, per node.Decides whether a relying party ID may be used to build an outbound URL.Why a value was rejected.Outcome ofRpIdValidator.validate(String): either an accepted ID or a rejection reason.A relying party ID thatRpIdValidatoraccepted: a normalized, lower-case, ASCII DNS hostname.Fetches the two native-app association files from a relying party's domain, and nothing else.WhatWellKnownFetchergot back from a relying party's server.Why no response was obtained.