Duo Universal Prompt Integration Fails with “Login Expired”
DUO has updated their app and now enforces stricter OIDC semantics; if the app does not complete the code/state exchange, the transaction fails with message_enum: 57.
The Duo prompt displays, push approval succeeds, but the login process ends with a “Login expired” error in Cerberus. Switching back to Duo’s Traditional Prompt resolves the issue.
Can you please provide commentary on an updated version that fully supports Duo Universal Prompt. I did submit a ticket #1212834
Thanks
1
-
I'm having the same issue in 2025.4.2.0
0 -
Hello Carl,
I am going to turn this into a ticket so we can assist you directly with this issue, and so we can track if this is on going with other users. Please look out for an email from us.
0
Please sign in to leave a comment.
Comments
2 comments