We are implementing a password-optional signup flow and are analyzing the response we receive. During this process, we call the following method:
OktaAuth.idx.register()
Upon resolving, we observe a property called expiresAt, which contains a datetime value roughly 5 minutes after the API call is completed. We would appreciate more details about this property, as we are noticing behavior.
Here’s a summary of the flow:
- Call the SDK function
OktaAuth.idx.register().
- User kept idle for 5 minutes. ( no SDK functions were triggered )
- After 5 minutes, call the proceed function to verify the OTP.
const inputValues = {
"verificationCode": "197277"
};
const newTransaction = await oktaAuth.idx.proceed(inputValues);
We then received an API response with the message “The session has expired.” Does the expiresAt
property play a role in this behavior? If so, could you provide more insight into how it works?
Note: we are using Angular and Okta Auth JS SDK
Many Thanks,
Anugrah