Issue with the authentication response if only username is passed

[HarshaVardhanAnde]

Describe the bug?

In OKTA Authentication Policy Rule, "User must authenticate with" is set to Possession Factor (or) Any 1 factor type (or) Any 2 factor types. For OKTA Authn API(Primary Authn) when only username is passed, in response we get all the authenticator factors list. But using Okta Idx dotnet sdk AuthenticatorAsync() method we are getting only password factor in authenticators list which is not expected.

OKTA Browser -
Endpoint - https://oie-tecnics-dev.oktapreview.com/idp/idx/identify
Payload - {"identifier":"username", "stateHandle":"statehandle-value"}
Response - https://jsonblob.com/1022053725833019392

SDK - AuthenticatorAsync() method
Payload - {"username" : "username"}
Response - https://jsonblob.com/1022050865690984448

What is expected to happen?

In authentication policies rule if "User must authenticate with" value is set to Possession Factor (or) Any 1 factor type (or) Any 2 factor types and when user gives only username in the payload we should get all the authenticators factors list as per the authentication policy rule set for the user.

What is the actual behavior?

In authentication policies rule if "User must authenticate with" value is set to is set to Possession Factor (or) Any 1 factor type (or) Any 2 factor types and when user gives only username in the payload for sdk AuthenticatorAync() method is returning only password factor in authenticators list.

Reproduction Steps?

1. In authentication policies rule if "User must authenticate with" value is set to is set to Possession Factor (or) Any 1 factor type (or) Any 2 factor types
2. Using sdk AuthenticatorAsync() method pass only the username in payload.

Additional Information?

No response

.NET Version

.NET Core 3.1

SDK Version

Okta.Idx.Sdk 2.2.1 (latest dotnet sdk)

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

[bryanapellanes-okta]

@HarshaVardhanAnde Thanks for reaching out and bringing this to our attention! We will need to investigate further, I've opened an internal ticket for reference: OKTA-512374

[HarshaVardhanAnde]

Thank you @bryanapellanes-okta for your quick response.

[bryanapellanes-okta]

@HarshaVardhanAnde Beginning preliminary investigation into this issue; I notice that the links you provide for the responses on jsonblob.com reference blobs that don't or no longer exist. Please provide the content of those responses here.

[HarshaVardhanAnde]

@bryanapellanes-okta Please find the latest responses in the JSON Blob
SDK - AuthenticatorAsync() method
Payload - {"username" : "username"}
Response - https://jsonblob.com/1011954371394813952

[gdperkins]

I am facing the same issue in a .net 9 environment and the okta.idx.sdk v2.4.6