Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 527: Duo MFA: pass new SID to subsequent API call to DuoSecurity (with backward compatibility) #532

Conversation

himanshu-neema
Copy link
Contributor

@himanshu-neema himanshu-neema commented Aug 4, 2020

Fixes issue: #527

Fix for Duo Security API change:

  • Store the new SID obtained in response from POST /frame/status ( duoSubmitURL in code )
  • Pass new SID in subsequent API call to POST /frame/status/<TxID> ( duoResultURL in code )

Bug fixes (this was causing infinite loop for Duo Push MFA failures) :

  • Certain code paths in verifyMfa returns nil error when in fact it should return an error: error.Wrap( ) replaced with error.New( ) : because wrapping nil err returns nil

Update 18th Aug 2020

We noticed API reverted back: hence made the change backward compatible in 6200cf3

@himanshu-neema
Copy link
Contributor Author

Hi @wolfeidau - Please review this PR when you get a chance and let me know what you think.

@himanshu-neema himanshu-neema changed the title Issue 527: Duo MFA: pass new SID to subsequent API call to DuoSecurity Issue 527: Duo MFA: pass new SID to subsequent API call to DuoSecurity (with backward compatibility) Aug 18, 2020
@wolfeidau wolfeidau merged commit 0d7ee0a into Versent:master Aug 23, 2020
@himanshu-neema
Copy link
Contributor Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants