This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 16 lines
!!! Overview
[{$pagename}] Confidence exists that the asserted [Digital Identity] is accurate within the [context].
Perhaps an email verification was used.
[{$pagename}] provides single factor remote network [authentication]. At [{$pagename}], identity proofing requirements are introduced, requiring presentation of identifying materials or information. A wide range of available [authentication methods] can be employed
[{$pagename}] allows any of the [token] methods of [LOA 3] or [LOA 4], as well as [passwords] and [PINs]. Successful [authentication] requires that the claimant prove through a secure [authentication] protocol that he or she controls the [token]. Use of a [Secure connection] to prevent Eavesdropper, replay, and on-line guessing [attackers] are prevented.
Long-term shared [authentication] secrets, if used, are __never__ revealed to any party except the claimant and verifiers operated by the [Credential Service Provider] ([CSP]); however, session (temporary) shared secrets may be provided to independent verifiers by the [CSP]. Approved [cryptographic] techniques are [required|MUST]. [Assertions] issued about claimants as a result of a successful [authentication] are either cryptographically authenticated by [relying Parties|Relying Party] (using Approved methods), or are obtained directly from a trusted party via a secure authentication protocol.
[{$pagename}] used frequently for self service applications.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]