JorisW.24808 (Customer) asked a question.
Okta Desktop MFA "parameters incorrect" error on login after upgrade to Okta Verify 6.10
When our users receive the Okta Verify app upgrade from version 6.9 to version 6.10, they can't login to their laptops anymore. As soon as they have entered their username and password, they don't get to the Okta Desktop MFA screen, but receive an error "Parameters Incorrect".
When we delete the app's cache folder, containing the Okta Verify database, the user can login again. But as soon as the laptop locks, they are back to the "Parameters incorrect" error.
What could it be? How can we help the users to be able to login again?
We have opened a ticket with the same issue. We have paused updates until we can find a solution.
Our case is the initial login with MFA prompt works. Locking and unlocking is where we see the issue.
I have done a fresh install, verified the Okta Identity Service is running.
I can see in the log that it looks like I cancelled the login.
I have found that inside the MFA grace period I get the error.
Outside the MFA grace period, it prompts for MFA and I can unlock.
Here's to hoping we have a solution soon.
Thank you Collin, what you see in the log (like if you cancelled the login) I see as well. We will test the outside-grace period login, we have set that to one hour, so we will have to wait for that to pass.
We have also paused the updates with the registry key. Hopefully this can be fixed soon.
A ticket is opened with Okta, but we still haven't been contacted yet.
Hi @JorisW.24808 (Customer) & @CollinL.43189 (Customer) , Thank you for reaching out to the Okta Community!
The Okta Verify for Windows release notes don't mention any explicit change that could have caused this, so I've checked with our colleagues from the Okta Support team and confirmed that we are seeing multiple reports of this issue and it is currently being investigated.
Please continue working directly with the assigned Technical Support Engineer to gather any relevant information that might be used for additional troubleshooting or a possible internal escalation.
If I receive confirmation of a fix, I'll post the relevant information here as soon as possible.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added
UPDATE 1:
The internal Engineering team has been involved and is currently investigating the root cause and working on a fix for the impacted customers.
I'll return once other information becomes available.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added
UPDATE 2:
Our Engineering team has identified the root cause and is looking into potentially rolling back the release. In the meantime there have been positive test in preview, so please coordinate with your TSEs on the Support tickets to check for potential ETAs for production and other updates.
I'll return once other information becomes available.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added
FINAL UPDATE:
The Okta Engineering team is now moving forward with the global deployment of Windows Okta Verify 6.10.2 and estimates that the full rollout to production will take some time.
In the meantime, please reach out to support for a copy of the `6.10.2` version to manually update and unblock yourselves a bit faster than the global rollout.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added