Describe the bug?
User has 3 enrollments for webauthn factor with 3 devices.
When webauthn factor has multiple enrollments with multiple security keys, their credential ids and display names are provided in "/challenge" endpoint response for authenticatorEnrollments key.
OKTA Endpoint : https://oie-tecnics-dev.oktapreview.com/idp/idx/challenge
OKTA Response : https://jsonblob.com/1051889283425910784
But while using this SDK method : SelectChallengeAuthenticatorAsync() with payload {"authenticatorId" : "{authenticatorId/factorId value}"} which is equivalent to /challenge endpoint, only one enrollment device info is returned.
SDK response : https://jsonblob.com/1051874885303025664
What is expected to happen?
Expecting all enrollments credentialIds and displaynames as provided in browser response.
What is the actual behavior?
Only one enrollment (latest enrolled) device info ie, credential Id is returned and display name is completely absent even in this single enrollment object.
Reproduction Steps?
- Enroll with multiple devices for webauthn factor for OIE tenant.
- Using okta-idx-dotnet sdk, perform primary authn using AuthenticateAsync() using payload
{
"Username" : "{username-value}",
"Password" : "{password-value}"
}
- Using webauth factor id from above response, call SelectChallengeAuthenticatorAsync() using payload
{ "AuthenticatorId" : "{factor-id-value}"}
- Only one enrollment (latest enrolled) device info ie, credential Id is returned. Expecting all enrollments credential ids and display names in response.
Additional Information?
No response
.NET Version
.NET Core 3.1
SDK Version
Okta.Idx.Sdk 2.2.5 (latest dotnet sdk)
Okta.Idx.Sdk 2.2.4, 2.2.3, 2.2.2 and all lower versions
OS version
Windows 11 :
BuildNumber Caption OSArchitecture Version
22000 Microsoft Windows 11 Pro 64-bit 10.0.22000
Windows 10 :
BuildNumber Caption OSArchitecture Version
19044 Microsoft Windows 10 Pro 64-bit 10.0.19044
Describe the bug?
User has 3 enrollments for webauthn factor with 3 devices.
When webauthn factor has multiple enrollments with multiple security keys, their credential ids and display names are provided in "/challenge" endpoint response for authenticatorEnrollments key.
OKTA Endpoint : https://oie-tecnics-dev.oktapreview.com/idp/idx/challenge
OKTA Response : https://jsonblob.com/1051889283425910784
But while using this SDK method : SelectChallengeAuthenticatorAsync() with payload {"authenticatorId" : "{authenticatorId/factorId value}"} which is equivalent to /challenge endpoint, only one enrollment device info is returned.
SDK response : https://jsonblob.com/1051874885303025664
What is expected to happen?
Expecting all enrollments credentialIds and displaynames as provided in browser response.
What is the actual behavior?
Only one enrollment (latest enrolled) device info ie, credential Id is returned and display name is completely absent even in this single enrollment object.
Reproduction Steps?
{
"Username" : "{username-value}",
"Password" : "{password-value}"
}
{ "AuthenticatorId" : "{factor-id-value}"}
Additional Information?
No response
.NET Version
.NET Core 3.1
SDK Version
Okta.Idx.Sdk 2.2.5 (latest dotnet sdk)
Okta.Idx.Sdk 2.2.4, 2.2.3, 2.2.2 and all lower versions
OS version
Windows 11 :
BuildNumber Caption OSArchitecture Version
22000 Microsoft Windows 11 Pro 64-bit 10.0.22000
Windows 10 :
BuildNumber Caption OSArchitecture Version
19044 Microsoft Windows 10 Pro 64-bit 10.0.19044