Backport of Fix OktaNumberChallenge into release/1.15.x #23604
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-secure-vault-core
force-pushed
the
backport/ui/VAULT-20694/fix-okta-number-challenge/reasonably-allowing-duck
branch
from
bc8b887 to
1fa7b4c
Compare
github-actions
bot
added
the
hashicorp-contributed-pr
|
Build Results: |
|
CI Results: |
Monkeychip
approved these changes
Oct 11, 2023
Monkeychip
deleted the
backport/ui/VAULT-20694/fix-okta-number-challenge/reasonably-allowing-duck
branch
|
I don't see a new image in Dockerhub yet. Do you now when we might get that? I'm running into this issue on the latest image from ~24 days ago. |
|
@WillBeebe I can't give you the exact date, but soon. They're working on the release branches for the minor patches this week. |
You're amazing! Thanks for letting me know. 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #23565 to be assessed for backporting due to the inclusion of the label backport/1.15.x.
The below text is copied from the body of the original PR.
Fix for this GitHub issue.
Seems like the regression happened in the ember upgrade—here. This is not a glimmer component so args don't work.
Overview of commits