We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Seems like okta backend is broken after #8143
* Okta auth failed: Post https://***.okta.comauthn/factors/*****/verify: dial tcp: lookup ***.okta.comauthn on 10.250.244.10:53: no such host
It looks like smth wrong with ulr. There is no "/" in path https://github.com/hashicorp/vault/blob/master/builtin/credential/okta/backend.go#L183 but here is https://github.com/hashicorp/vault/blob/master/builtin/credential/okta/backend.go#L103
To Reproduce Steps to reproduce the behavior:
vault login -method=okta username=*** password=***
Environment:
1.4
Additional context Add any other context about the problem here. This behaviour is only in vault 1.4 Vault 1.3.4 works perfect
The text was updated successfully, but these errors were encountered:
Hi @moskitone,
Thank you for the bug report. I agree with your analysis. I will work on a fix which will hopefully appear in the next point release.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Seems like okta backend is broken after #8143
It looks like smth wrong with ulr. There is no "/" in path https://github.com/hashicorp/vault/blob/master/builtin/credential/okta/backend.go#L183
but here is
https://github.com/hashicorp/vault/blob/master/builtin/credential/okta/backend.go#L103
To Reproduce
Steps to reproduce the behavior:
vault login -method=okta username=*** password=***
Environment:
1.4
):Additional context
Add any other context about the problem here.
This behaviour is only in vault 1.4
Vault 1.3.4 works perfect
The text was updated successfully, but these errors were encountered: