Class StrongAuthSupport
java.lang.Object
com.iizix.user.StrongAuthSupport
What the strong authentication of this build fully supports today (CC-FIX-SIGNIN-STRONG-SUPPORTED-MAX; the owner's rule of 2026-11-07: "you should not be able to set a value with a higher protection or stronger authentication than the current fully supported maximum"): the factors a policy may name, hence the highest
count and floor a setting may ask for. Every place that accepts a value of a StrongAuthPolicy reads this one decision: the parser of the six keys, the verification of the server settings, of an environment's custom application settings and of an application's definition, the load of an application's module settings, and the raise of an application's code. A value above it is refused where it is set, naming what is supported; it is never accepted and capped, and never accepted to fail later at a sign-in.One decision, one seam (built like the license enforcement switch of order CC-LICENSE-ENFORCE-SWITCH, com.iizix.license.LicenseEnforcement):
- the build:
buildFactors(), a constant of the build behind a method - the factors the shipped server verifies and every client can do:passkeyandtotp. The factorbiometric(a hardware-bound biometric device key of the iiziRun app, section 2 of the design of order 475) is known to the code,StrongAuthPolicy.ALL_FACTORS, and its flow is written, but no client can do it until the device-key orders: it is NOT supported, so no setting can name it and no count can reach 3. Widening the build's answer is a source change of the release that supports the factor; - the lab override: the class
LAB_CLASS(StrongAuthLabof the test support bundlecom.iizix.tests.support), reached reflectively, whoseread()answers the factors a test or a rig declared supported, or null for none. The class lives outside every shipped bundle: no release of iiziServer or iiziGo carries it, so a release reads no override and no system property, environment variable, setting, configuration file or user interface a customer reaches can widen what is supported. The rig turnsbiometricon with it to keep the dormant future path tested.
- Author:
- Christopher Mindus
Field Summary
FieldsMethod Summary
Modifier and TypeMethodDescriptionGets the factors this build fully supports by itself, whatever a lab declared:passkeyandtotpuntil the release that supports the biometric device key.factors()Gets the factors supported today: what the lab override declares when it is present and set, else the build's answer.static booleanChecks if the lab override is in force: the lab class is present and declares the factors.static booleanisSupported(String factor) Checks if a factor is supported today.static Stringlist()Gets the supported factors as a refusal names them.static intmaxCount()Gets the highest count a policy may ask for today: as many different factors as are supported.static StringGets what is supported as a refusal says it, after the value refused.
Field Details
LAB_CLASS
The fully qualified name of the lab override class, "com.iizix.tests.support.StrongAuthLab": a class of the test support bundle, never of a shipped one, with a public static methodSet<String> read().- See Also:
Method Details
buildFactors
Gets the factors this build fully supports by itself, whatever a lab declared:passkeyandtotpuntil the release that supports the biometric device key.- Returns:
- The factors, in the order of
StrongAuthPolicy.ALL_FACTORS; unmodifiable.
factors
Gets the factors supported today: what the lab override declares when it is present and set, else the build's answer. What a policy may name infactorsandmandatory, and the default offactors.- Returns:
- The factors, in the order of
StrongAuthPolicy.ALL_FACTORS; unmodifiable, never empty.
maxCount
public static int maxCount()Gets the highest count a policy may ask for today: as many different factors as are supported.- Returns:
- The count, 2 until the biometric device key is supported.
isSupported
Checks if a factor is supported today.- Parameters:
factor- The factor, null for none.- Returns:
- true when a policy may name it.
isLabOverride
public static boolean isLabOverride()Checks if the lab override is in force: the lab class is present and declares the factors.- Returns:
- true when a test or a rig decides what is supported; always false in a release.
list
Gets the supported factors as a refusal names them.- Returns:
- E.g.
"passkey, totp".
supportedText
Gets what is supported as a refusal says it, after the value refused.- Returns:
- E.g.
"the factors supported today are passkey, totp".