You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: Src/Fido2/Fido2.cs
+12-31
Original file line number
Diff line number
Diff line change
@@ -26,37 +26,13 @@ public Fido2(
26
26
/// <summary>
27
27
/// Returns CredentialCreateOptions including a challenge to be sent to the browser/authenticator to create new credentials.
28
28
/// </summary>
29
-
/// <param name="user"></param>
30
-
/// <param name="excludeCredentials">Recommended. This member is intended for use by Relying Parties that wish to limit the creation of multiple credentials for the same account on a single authenticator. The client is requested to return an error if the new credential would be created on an authenticator that also contains one of the credentials enumerated in this parameter.</param>
31
-
/// <param name="extensions"></param>
29
+
/// <param name="requestNewCredentialParams">The input arguments for generating CredentialCreateOptions</param>
/// Returns CredentialCreateOptions including a challenge to be sent to the browser/authenticator to create new credentials.
43
-
/// </summary>
44
-
/// <param name="user"></param>
45
-
/// <param name="excludeCredentials">Recommended. This member is intended for use by Relying Parties that wish to limit the creation of multiple credentials for the same account on a single authenticator. The client is requested to return an error if the new credential would be created on an authenticator that also contains one of the credentials enumerated in this parameter.</param>
46
-
/// <param name="authenticatorSelection"></param>
47
-
/// <param name="attestationPreference">This member is intended for use by Relying Parties that wish to express their preference for attestation conveyance. The default is none.</param>
/// The input arguments for generating AssertionOptions
9
+
/// </summary>
10
+
publicsealedclassGetAssertionOptionsParams
11
+
{
12
+
/// <summary>
13
+
/// This OPTIONAL member is used by the client to find authenticators eligible for this authentication ceremony. It can be used in two ways:
14
+
///
15
+
/// * If the user account to authenticate is already identified (e.g., if the user has entered a username), then the Relying Party SHOULD use this member to list credential descriptors for credential records in the user account. This SHOULD usually include all credential records in the user account.
16
+
/// The items SHOULD specify transports whenever possible. This helps the client optimize the user experience for any given situation. Also note that the Relying Party does not need to filter the list when requesting user verification — the client will automatically ignore non-eligible credentials if userVerification is set to required.
17
+
/// See also the § 14.6.3 Privacy leak via credential IDs privacy consideration.
18
+
/// * If the user account to authenticate is not already identified, then the Relying Party MAY leave this member empty or unspecified. In this case, only discoverable credentials will be utilized in this authentication ceremony, and the user account MAY be identified by the userHandle of the resulting AuthenticatorAssertionResponse. If the available authenticators contain more than one discoverable credential scoped to the Relying Party, the credentials are displayed by the client platform or authenticator for the user to select from (see step 7 of § 6.3.3 The authenticatorGetAssertion Operation).
19
+
///
20
+
/// If not empty, the client MUST return an error if none of the listed credentials can be used.
21
+
///
22
+
/// The list is ordered in descending order of preference: the first item in the list is the most preferred credential, and the last is the least preferred.
/// This OPTIONAL member specifies the Relying Party's requirements regarding user verification for the get() operation. The value SHOULD be a member of UserVerificationRequirement but client platforms MUST ignore unknown values, treating an unknown value as if the member does not exist. Eligible authenticators are filtered to only those capable of satisfying this requirement.
/// The Relying Party MAY use this OPTIONAL member to provide client extension inputs requesting additional processing by the client and authenticator.
/// The input arguments for generating CredentialCreateOptions
9
+
/// </summary>
10
+
publicsealedclassRequestNewCredentialParams
11
+
{
12
+
/// <summary>
13
+
/// This member contains names and an identifier for the user account performing the registration. Its value’s name, displayName and id members are REQUIRED. id can be returned as the userHandle in some future authentication ceremonies, and is used to overwrite existing discoverable credentials that have the same rp.id and user.id on the same authenticator. name and displayName MAY be used by the authenticator and client in future authentication ceremonies to help the user select a credential, but are not returned to the Relying Party as a result of future authentication ceremonies
14
+
/// </summary>
15
+
publicrequiredFido2UserUser{get;init;}
16
+
17
+
/// <summary>
18
+
/// The Relying Party SHOULD use this OPTIONAL member to list any existing credentials mapped to this user account (as identified by user.id). This ensures that the new credential is not created on an authenticator that already contains a credential mapped to this user account. If it would be, the client is requested to instead guide the user to use a different authenticator, or return an error if that fails.
/// The Relying Party MAY use this OPTIONAL member to specify capabilities and settings that the authenticator MUST or SHOULD satisfy to participate in the create() operation. See § 5.4.4 Authenticator Selection Criteria (dictionary AuthenticatorSelectionCriteria).
/// The Relying Party MAY use this OPTIONAL member to specify a preference regarding attestation conveyance. Its value SHOULD be a member of AttestationConveyancePreference. Client platforms MUST ignore unknown values, treating an unknown value as if the member does not exist.
/// The Relying Party MAY use this OPTIONAL member to provide client extension inputs requesting additional processing by the client and authenticator. For example, the Relying Party may request that the client returns additional information about the credential that was created.
0 commit comments