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
the above code executes fine until when our okta admin go-ahead and add a new behavior ("NEW_DEVICE") in OKTA console. After the new behavior got added to OKTA, whenever a user tries to login OKTA transaction response has MFA_REQUIRED and I think deviceToken is ignored in the request.
What is expected to happen?
OKTA should consider / respect deviceToken sent as part of the request headers as long it same when sent along with authentication request.
What is the actual behavior?
SDK shouldn't expect MFA_REQUIRED for every authentication request when NEW_DEVICE behavior is added in OKTA dashboard / console.
Reproduction Steps?
Create OIDC Application
Create SMS / Email MFA Factors
Add a Behavior trigger MFA for NEW_DEVICE
use custom signIn using getAuthClient and pass username, password, deviceToken in context
Additional Information?
No response
SDK Version
v2.6.0
Build Information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug?
the above code executes fine until when our okta admin go-ahead and add a new behavior ("NEW_DEVICE") in OKTA console. After the new behavior got added to OKTA, whenever a user tries to login OKTA transaction response has MFA_REQUIRED and I think deviceToken is ignored in the request.
What is expected to happen?
OKTA should consider / respect deviceToken sent as part of the request headers as long it same when sent along with authentication request.
What is the actual behavior?
SDK shouldn't expect MFA_REQUIRED for every authentication request when NEW_DEVICE behavior is added in OKTA dashboard / console.
Reproduction Steps?
Additional Information?
No response
SDK Version
v2.6.0
Build Information
No response
The text was updated successfully, but these errors were encountered: