Skip to content

Conversation

hellobontempo
Copy link
Contributor

Description

After consulting with security folks, we decided to hold off on implementing "autocomplete" functionality in the login form for now. There's concern this will upset the security expectations of some users.

We can revisit this if a strong case comes up to support autocomplete. If we end up making this change, we will likely only support autocomplete for non-token fields.

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@hellobontempo hellobontempo added this to the 1.20.0-rc milestone Apr 29, 2025
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Apr 29, 2025
@hellobontempo hellobontempo marked this pull request as ready for review April 29, 2025 18:44
@hellobontempo hellobontempo requested a review from a team as a code owner April 29, 2025 18:44
Copy link

github-actions bot commented Apr 29, 2025

CI Results:
All Go tests succeeded! ✅

Copy link

Build Results:
All builds succeeded! ✅

@@ -20,15 +18,4 @@ interface Field {
export default class AuthFields extends Component<Args> {
// token or password should render as "password" types, otherwise render text inputs
setInputType = (field: string) => (['token', 'password'].includes(field) ? 'password' : 'text');
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is small enough it could happen in the component, but I thought the interfaces might be helpful in the future:

interface Args {
loginFields: Field[];
}
interface Field {
name: string; // sets input name
label?: string; // label will be "name" capitalized unless label exists
helperText?: string;
}

If they seem unnecessary, happy to remove the backing class!

@hellobontempo hellobontempo merged commit ba3f736 into main Apr 29, 2025
41 checks passed
@hellobontempo hellobontempo deleted the VAULT-35410/remove-autocomplete branch April 29, 2025 19:36
drivera258 pushed a commit that referenced this pull request Apr 30, 2025
* set autocomplete to off

* add comment

* update test
Erfankam pushed a commit to Erfankam/vault that referenced this pull request Sep 1, 2025
* set autocomplete to off

* add comment

* update test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants