+++ This bug was initially created as a clone of Bug #1957591 +++

Description of problem:

The following text is from the reporting user:
~~~
Vulnerability Scanner has identified Vulnerability titled:AutoComplete Attribute Not Disabled for Password in Form Based Authentication in Pacemaker PCSD. Detected on 2224 port which is pcsd port.

As per scanner recommendation "Contact the vendor to have the AutoComplete attribute disabled for the password field in all forms. The AutoComplete attribute should also be disabled for the user ID field.

Developers can add the following attribute to the form or input element: autocomplete="off"

This attribute prevents the browser from prompting the user to save the populated form values for later reuse.

Most browsers no longer honor autocomplete="off" for password input fields. These browsers include Chrome, Firefox, Microsoft Edge, IE, Opera

However, there is still an ability to turn off autocomplete through the browser and that is recommended for a shared computing environment.

"Since the ability to turn autocomplete off for password inputs fields is controlled by the user it is highly recommended for application to enforce strong password rules.
~~~

More detail about the attribute here:

• https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete

The practical risk that's present here seems very low. Nonetheless, this seems like a straightforward change if we decide to make it.

The reporter opened a case against RHEL 7.9. I'm opening this BZ against RHEL 8. We can clone if desired.

Version-Release number of selected component (if applicable):

pcs-0.10.6-4.el8

How reproducible:

Always

Steps to Reproduce:

Trivial; check for autocomplete attribute on the password input of the authentication form in the pcsd web UI.

Actual results:

`autocomplete="off"` attribute not present.

Expected results:

`autocomplete="off"` attribute present.

— Additional comment from Reid Wahl on 2021-05-06 07:50:41 CEST —

The reporter stated that there is no CVE associated with this vulnerability scan result.

— Additional comment from Huzaifa S. Sidhpurwala on 2021-05-24 06:28:24 CEST —

Really looks like security hardening to me, and that too borderline. So this is not a security flaw, hence no CVE