Package com.iizix.server.user.mfa
package com.iizix.server.user.mfa
- ClassDescriptionThe database of the second factor of the users (SignIn L-6; D-24 of the SignIn survey): the tables
IZS.USER_MFAandIZS.USER_MFA_CODESofcreateMFATables.sqlbeside this class, and the statements on them.A recovery code, as stored.The second factor of a user, as stored.The class used to provide an MFA authentication using a TOTP based QR code (RFC 6238).Enum to define valid hashing algorithms.The sign-in policy of the applications of this server (SignIn L-6; section 5 of the SignIn flow design, its decision D-11): the settings of the server,$signIn.*in the server settings, with what the application overrides,signIn.*in itsmoduleAppsettings.The strong authentication policy of an application as its sources resolved it, or the problem that keeps them from resolving (CC-SIGNIN-STRONG-POLICY).The rules of the sign-in settings an administrator edits in ServerAdmin's Sign-in page (CC-SERVERADMIN-SIGNIN-PAGE, order 510; the design of the survey CC-SURVEY-SERVERADMIN-SIGNIN-SETTINGS, its sections 4.2 to 4.6): what each setting means, its range and its default, how it is written to the configuration (with the property class iiziGo's catalog names, so the file keeps the form iiziGo reads and writes), which change lowers the administrators' protection (guard G2), which change would lock the administrators out (guard G1: a second step required of them while ServerAdmin's own application offers no method they could set up), which change has a consequence a dialog states before it is made (guard G3), and the one audit line per changed key.The consequence of a change that a dialog states before the change is made (guard G3).The effective value of a policy setting for an application, and where it comes from.What kind of value a setting takes.Where a setting lives.The settings of the page, each with its key in its container, its level, its kind and its range.The guards of a strong authentication policy an administrator sets in ServerAdmin (CC-SERVERADMIN-STRONG-AUTH; section 6 of the design of order 475, SA-D-11; the rows SM-D-2, SM-D-3 and SM-D-4 of order 542): what ServerAdmin's Add/Edit application dialog and its Sign-in page refuse before anything is written, so that no setting locks the administrators out of the server they administer.What is known of an administrator for the save guard: the name and the factors enrolled now.The second factor of the users of the server (SignIn L-6, the survey's section 9.3 item 7, and sections 3.5 and 6 of the SignIn flow design): whatMFAUserandcom.iizix.totpcould not do on their own.The answer to a code.A confirmed enrollment.A sign-in that waits for its second factor.What became of a request.A refusal of a request that answers with data.The progress of a sign-in held under a strong authentication policy (CC-SIGNIN-STRONG-POLICY, section 2.2 of the design of order 475): the policy, the target this client reaches, the factors verified so far, each at most once, and whether a recovery code was used - which counts as no factor and lets the user re-enroll a replacement (SA-D-10).The names of the entry an authenticator app shows for a user's enrollment, as the enrollment's QR code gave them (CC-FIX-SIGNIN-RECOVERY): what the code page names, so that the user picks the right entry among several.