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

Backport of UI: Redirect after logging in from token expiry into release/1.16.x #25340

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #25335 to be assessed for backporting due to the inclusion of the label backport/1.16.x.

The below text is copied from the body of the original PR.


Adds a redirect back to the current URL if the user's token expires and they click "reauthenticate".

This PR fixes #10963


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/ui/redirect-after-token-expire/vaguely-mutual-bobcat branch from 8e80a11 to 35169c4 Compare February 9, 2024 18:39
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Feb 9, 2024
@hashishaw hashishaw added the ui label Feb 9, 2024
@hashishaw hashishaw added this to the 1.16.0-rc1 milestone Feb 9, 2024
@hashishaw hashishaw enabled auto-merge (squash) February 9, 2024 18:41
Copy link

github-actions bot commented Feb 9, 2024

Build Results:
All builds succeeded! ✅

Copy link

github-actions bot commented Feb 9, 2024

CI Results:
All Go tests succeeded! ✅

@hashishaw hashishaw merged commit 2c35369 into release/1.16.x Feb 9, 2024
27 of 29 checks passed
@hashishaw hashishaw deleted the backport/ui/redirect-after-token-expire/vaguely-mutual-bobcat branch February 9, 2024 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants