-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Panic on attempting MFA with DUO Security #2030
Comments
Im getting the same panic when trying duo. Running Vault v0.6.2. |
From the vault server, can you attempt to perform a connectivity test to the Duo service? Either via netcat or curl to |
I am seeing this error right now. @broamski can you advise on how to construct the duo API endpoint from the Vault config? Since I am seeing this locally, I may take a stab at debugging it. |
The issue is sporadic, starting and stopping without any changes in okta/duo configuration. By the time I attempted the repro with a locally-built Vault (as opposed to a locally-executed 0.9.1 release), the issue was no longer occurring. |
A current panic would help, because the line being shown in the panic above doesn't correspond to anything useful in modern Vault. I didn't see anything around it that should be problematic, either. |
The line number I am seeing (in 0.9.1) is the same as the above: vault/helper/mfa/duo/path_duo_access.go Line 72 in 87b6919
Based on https://help.duo.com/s/article/1338?language=en_US "A message_detail key may be present if additional information is available (like the specific parameter that caused the error)" that
Logs from earlier (pardon docker-compose line prefix):
|
Doh, somehow I was looking at line 62. |
@jefferai I don't think #3832 will fix - the line numbers at master are shifted one from the line numbers in v0.9.1 (see permalink above). The panic is on the line with the I think the problem has to be either |
@jgiles Check master, that's already done. |
Ah I hadn't seen ec19c6c Pardon the nitpick, but I don't think you want to throw out As an end-user, the panic itself isn't the problem; the problem is that you don't see any helpful error message. |
It's pretty unclear what one should expect at any time, especially given that key parts of their API don't behave as documented. (Their Go SDK is, somehow, even worse.) I'll attempt to figure something out though. |
This ought to do it: https://github.com/hashicorp/vault/pull/3834/files |
Thanks! Now next time this happens we'll have some idea what's actually going wrong with Duo. |
If you notice the date of my original post, the first day I encountered this problem happened to be the day of the DYN DNS attack in 2016. When I posted this, I hadn't put the two events together, but not long afterward I did. At the time I was prototyping this solution, but never returned to it after this failure. Edit... Oops, I just re-read the original post and I see that I did mention about the DDOS attacks. |
I set up user/password authentication to vault according to the instructions, then added DUO multi-factor authentication. I had this working on Thursday 10/19, but then Friday morning it was no longer working.
The client does the following:
On the vault server, the console output is:
On Friday I didn't research the problem because I figured the DDOS attacks going on could effect the MFA services, but this week the problem persists. I've made sure the host configured for duo security is accessible from the server and DNS properly resolves the server to an IP address there. The traffic from the server is being run through a proxy server and I can see log entries from the proxy server indicating that a connection is happening to the correct domain name. I have tried running the vault server on 2 different hosts with the same result.
The text was updated successfully, but these errors were encountered: