Added validation of FIPS password length

[Santhosh-CloudB]

See JENKINS-72332.

Testing done

FIPS Enabled Jenkins requires password to be 112 bits(14 chars) minimum. While creating a User, when the password is short, it was showing error in console and navigating to error page. Now a validation has been added to check the password length.

The error couldnt be caught since its unchecked exception and its been caused in the line of code where framework's encode method is called.this doesnt allow adding a new exception apart from the one defined in the interface.

Testing has been done in FIPS enabled Docker container.

Proposed changelog entries

• Fips mode now requires a minimum of 14 characters for a password.

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[Santhosh-CloudB]

Issue created in Jenkins.io - https://issues.jenkins.io/browse/JENKINS-72332

[timja]

Please restore the pull request template https://github.com/jenkinsci/jenkins/blob/master/.github/PULL_REQUEST_TEMPLATE.md

[olamy]

LGTM
But @Santhosh-CloudB you need to restore the template to have proper release notes, link to Jira etc..
Thanks

[Santhosh-CloudB]

Please restore the pull request template https://github.com/jenkinsci/jenkins/blob/master/.github/PULL_REQUEST_TEMPLATE.md

done

[Santhosh-CloudB]

done

[olamy]

@timja @daniel-beck, this looks to be good to merge now. Or something else you want to be changed?
Thanks

[timja]

The changelog template is broken please just copy and paste the whole template back in as text and edit it appropriately

[olamy]

The changelog template is broken please just copy and paste the whole template back in as text and edit it appropriately

@timja should be better now.

@Santhosh-CloudB I fixed the description with the changelog template

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

[Santhosh-CloudB]

/label ready-for-merge

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

@timja - Looks its not merged yet. can you pls merge it?

[welcome]

Congratulations on getting your very first Jenkins core pull request merged 🎉🥳

This is a fantastic achievement, and we're thrilled to have you as part of our community! Thank you for your valuable input, and we look forward to seeing more of your contributions in the future!

We would like to invite you to join the community chats and forums to meet other Jenkins contributors 😊
Don't forget to check out the participation page to learn more about how to contribute to Jenkins.