Skip to content

JKNS-859: Replace jbcrypt with Spring Security BCryptPasswordEncoder#2338

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
kunalmemane:JKNS-859-fix-jbcrypt-with-spring-security
Mar 20, 2026
Merged

JKNS-859: Replace jbcrypt with Spring Security BCryptPasswordEncoder#2338
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
kunalmemane:JKNS-859-fix-jbcrypt-with-spring-security

Conversation

@kunalmemane
Copy link
Copy Markdown
Member

@kunalmemane kunalmemane commented Feb 27, 2026

Jenkins LTS 2.516.1 removed the jbcrypt library from the WAR, breaking password hashing in OpenShift Jenkins. Updated password encoding to use Spring Security's BCryptPasswordEncoder instead.

  • Added Java source files for PasswordEncoder and PasswordChecker under jenkins-bcrypt-util/ (replaces the prebuilt password-encoder.jar)
  • Build password-encoder.jar at container startup from these sources using spring-security-crypto from the Jenkins WAR
  • Update classpath in jenkins-common.sh to use WAR lib jars for runtime dependencies

Ref:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 27, 2026

@kunalmemane: This pull request references JKNS-859 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Jenkins 2.509 removed the jbcrypt library from the WAR. Updated password-encoder.jar to use Spring Security's BCryptPasswordEncoder and adjust the classpath in jenkins-common.sh to resolve dependencies from the WAR lib directory.

ref:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from avinal and prdhamdh February 27, 2026 08:34
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 27, 2026

@kunalmemane: This pull request references JKNS-859 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Jenkins 2.509 removed the jbcrypt library from the WAR. Updated password-encoder.jar to use Spring Security's BCryptPasswordEncoder and adjust the classpath in jenkins-common.sh to resolve dependencies from the WAR lib directory.

ref:

Also see:

This is the codebase for password-encoder.jar to use Spring Security's BCryptPasswordEncoder

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 27, 2026

@kunalmemane: This pull request references JKNS-859 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Jenkins 2.509 removed the jbcrypt library from the WAR. Updated password-encoder.jar to use Spring Security's BCryptPasswordEncoder and adjust the classpath in jenkins-common.sh to resolve dependencies from the WAR lib directory.

ref:

Also see:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@kunalmemane kunalmemane force-pushed the JKNS-859-fix-jbcrypt-with-spring-security branch 3 times, most recently from e05344a to e52acb3 Compare February 27, 2026 10:22
Comment thread 2/contrib/jenkins/jenkins-common.sh Outdated
Comment thread 2/contrib/jenkins/jenkins-common.sh Outdated
@kunalmemane kunalmemane force-pushed the JKNS-859-fix-jbcrypt-with-spring-security branch 2 times, most recently from fcb1c9d to 327b633 Compare February 27, 2026 12:29
@kunalmemane kunalmemane force-pushed the JKNS-859-fix-jbcrypt-with-spring-security branch from 327b633 to 1d2d719 Compare March 9, 2026 14:10
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 9, 2026

@kunalmemane: This pull request references JKNS-859 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Jenkins LTS 2.516.1 removed the jbcrypt library from the WAR, breaking password hashing in OpenShift Jenkins. Updated password encoding to use Spring Security's BCryptPasswordEncoder instead.

  • Added Java source files for PasswordEncoder and PasswordChecker under jenkins-bcrypt-util/ (replaces the prebuilt password-encoder.jar)
  • Build password-encoder.jar at container startup from these sources using spring-security-crypto from the Jenkins WAR
  • Update classpath in jenkins-common.sh to use WAR lib jars for runtime dependencies

Ref:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@kunalmemane kunalmemane force-pushed the JKNS-859-fix-jbcrypt-with-spring-security branch from 1d2d719 to 0f9aff6 Compare March 9, 2026 14:19
@kunalmemane
Copy link
Copy Markdown
Member Author

/test images

@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

@kunalmemane
Copy link
Copy Markdown
Member Author

/test images

1 similar comment
@kunalmemane
Copy link
Copy Markdown
Member Author

/test images

@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

1 similar comment
@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

@kunalmemane kunalmemane force-pushed the JKNS-859-fix-jbcrypt-with-spring-security branch 4 times, most recently from 724dfa6 to 0f9aff6 Compare March 10, 2026 09:19
@kunalmemane
Copy link
Copy Markdown
Member Author

/retest

Jenkins LTS 2.516.1 removed the jbcrypt library from the WAR, breaking
password hashing in OpenShift Jenkins. Updated password encoding to
use Spring Security's BCryptPasswordEncoder instead.

- Added Java source files for PasswordEncoder and PasswordChecker
  under jenkins-bcrypt-util/ (replaces the prebuilt password-encoder.jar)
- Build password-encoder.jar at container startup from these sources
  using spring-security-crypto from the Jenkins WAR
- Update classpath in jenkins-common.sh to use WAR lib jars for
  runtime dependencies
@kunalmemane kunalmemane force-pushed the JKNS-859-fix-jbcrypt-with-spring-security branch from 0f9aff6 to ecedb03 Compare March 11, 2026 15:04
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 11, 2026

@kunalmemane: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security ecedb03 link false /test security

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@prdhamdh
Copy link
Copy Markdown
Contributor

/lgtm
/approve
/label backport-risk-assessed
/label px-approved
/label docs-approved
/label qe-approved

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR qe-approved Signifies that QE has signed off on this PR labels Mar 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 20, 2026

@kunalmemane: This pull request references JKNS-859 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Jenkins LTS 2.516.1 removed the jbcrypt library from the WAR, breaking password hashing in OpenShift Jenkins. Updated password encoding to use Spring Security's BCryptPasswordEncoder instead.

  • Added Java source files for PasswordEncoder and PasswordChecker under jenkins-bcrypt-util/ (replaces the prebuilt password-encoder.jar)
  • Build password-encoder.jar at container startup from these sources using spring-security-crypto from the Jenkins WAR
  • Update classpath in jenkins-common.sh to use WAR lib jars for runtime dependencies

Ref:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kunalmemane, prdhamdh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2026
@prdhamdh
Copy link
Copy Markdown
Contributor

/verified by @prdhamdh

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@prdhamdh: This PR has been marked as verified by @prdhamdh.

Details

In response to this:

/verified by @prdhamdh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 94557ed into openshift:master Mar 20, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants