|
+5.4 Wallet Activation ---+5.4.1 Key Storage |
5.4 Wallet ActivationThe subscriber-controlled wallet SHALL require the presentation of an activation factor from the subscriber for the following actions that result in the creation of a signed artifact from the wallet’s signing keys: Providing proof of possession of the wallet’s signing key to the CSP during the issuance process
Signing the assertion for presentation to the RP
The subscriber-controlled wallet SHOULD require the presentation of an activation factor before any other operations that result in the creation of a signed artifact from the wallet’s signing keys. For example, using the wallet as an authenticator at AAL2 or above requires the presentation of an activation factor as per Sec. 3.2.10 of [SP800-63B]. The wallet MAY request the reissuance of previously issued attribute bundles from the same CSP without requiring subscriber involvement. For subscriber-controlled wallets that run on a device that the subscriber controls, the submission of the activation factor SHALL be a separate operation from the unlocking of the host device (e.g., smartphone), although the same activation factor used to unlock the host device MAY be used in the activation operation. Organizations MAY relax this requirement for subscriber-controlled wallets managed by or on behalf of the CSP (e.g., via mobile device management) and that are constrained to have short, organization-determined inactivity timeouts and device activation factors that meet the above requirements. Additional discussion of activation factors for authenticators is found in Sec. 3.2.10 of [SP800-63B]. For subscriber-controlled wallets that are hosted on a remote service, activation of the wallet is performed using an authenticator that is registered to the wallet service. This authenticator MAY be separate from those bound to the subscriber account at the CSP. 1. Prehľad
1.1 Odkazy1.2 Identifikované požiadavky1.3 Súvisiace predpisy2. Identifikované požiadavky
3. Súvisiace predpisy
|