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.Models/CredentialCreateOptions.cs
+4-4
Original file line number
Diff line number
Diff line change
@@ -15,27 +15,27 @@ public sealed class CredentialCreateOptions
15
15
/// Its value’s id member specifies the relying party identifier with which the credential should be associated.If omitted, its value will be the CredentialsContainer object’s relevant settings object's origin's effective domain.
/// This member contains data about the user account for which the Relying Party is requesting attestation.
22
22
/// Its value’s name, displayName and id members are required.
23
23
/// </summary>
24
24
[JsonPropertyName("user")]
25
-
publicFido2UserUser{get;set;}
25
+
publicrequiredFido2UserUser{get;set;}
26
26
27
27
/// <summary>
28
28
/// Must be generated by the Server (Relying Party)
29
29
/// </summary>
30
30
[JsonPropertyName("challenge")]
31
31
[JsonConverter(typeof(Base64UrlConverter))]
32
-
publicbyte[]Challenge{get;set;}
32
+
publicrequiredbyte[]Challenge{get;set;}
33
33
34
34
/// <summary>
35
35
/// This member contains information about the desired properties of the credential to be created. The sequence is ordered from most preferred to least preferred. The platform makes a best-effort to create the most preferred credential that it can.
/// This member specifies a time, in milliseconds, that the caller is willing to wait for the call to complete. This is treated as a hint, and MAY be overridden by the platform.
Copy file name to clipboardexpand all lines: Src/Fido2.Models/Objects/CredentialPropertiesOutput.cs
+2-3
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,12 @@ public class CredentialPropertiesOutput
12
12
/// This OPTIONAL property, known abstractly as the resident key credential property (i.e., client-side discoverable credential property), is a Boolean value indicating whether the PublicKeyCredential returned as a result of a registration ceremony is a client-side discoverable credential. If rk is true, the credential is a discoverable credential. if rk is false, the credential is a server-side credential. If rk is not present, it is not known whether the credential is a discoverable credential or a server-side credential.
13
13
/// </summary>
14
14
[JsonPropertyName("rk")]
15
-
publicboolRk{get;set;}
16
-
15
+
publicboolRk{get;init;}
17
16
18
17
/// <summary>
19
18
/// This OPTIONAL property is a human-palatable description of the credential’s managing authenticator, chosen by the user.
Copy file name to clipboardexpand all lines: Src/Fido2.Models/Objects/KeyProtection.cs
+4
Original file line number
Diff line number
Diff line change
@@ -19,21 +19,25 @@ public enum KeyProtection
19
19
/// </summary>
20
20
[EnumMember(Value="software")]
21
21
SOFTWARE=1,
22
+
22
23
/// <summary>
23
24
/// This flag should be set if the authenticator uses hardware-based key management. Exclusive in authenticator metadata with KEY_PROTECTION_SOFTWARE
24
25
/// </summary>
25
26
[EnumMember(Value="hardware")]
26
27
HARDWARE=2,
28
+
27
29
/// <summary>
28
30
/// This flag should be set if the authenticator uses the Trusted Execution Environment [TEE] for key management. In authenticator metadata, this flag should be set in conjunction with KEY_PROTECTION_HARDWARE. Exclusive in authenticator metadata with KEY_PROTECTION_SOFTWARE, KEY_PROTECTION_SECURE_ELEMENT
29
31
/// </summary>
30
32
[EnumMember(Value="tee")]
31
33
TEE=4,
34
+
32
35
/// <summary>
33
36
/// This flag should be set if the authenticator uses a Secure Element [SecureElement] for key management. In authenticator metadata, this flag should be set in conjunction with KEY_PROTECTION_HARDWARE. Exclusive in authenticator metadata with KEY_PROTECTION_TEE, KEY_PROTECTION_SOFTWARE
34
37
/// </summary>
35
38
[EnumMember(Value="secure_element")]
36
39
SECURE_ELEMENT=0x8,
40
+
37
41
/// <summary>
38
42
/// This flag must be set if the authenticator does not store (wrapped) UAuth keys at the client, but relies on a server-provided key handle. This flag must be set in conjunction with one of the other KEY_PROTECTION flags to indicate how the local key handle wrapping key and operations are protected. Servers may unset this flag in authenticator policy if they are not prepared to store and return key handles, for example, if they have a requirement to respond indistinguishably to authentication attempts against userIDs that do and do not exist. Refer to [UAFProtocol] for more details.
0 commit comments