-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins Version 2.479.3 running on Debian Bookworm.
When saving the security configuration, the already encrypted Active Directory password of the Jenkins config.xml was re-encrypted. As a result, the account could no longer connect to the domain and all users no longer had access to the Jenkins Server. In addition, a port was added to the address.
We had to import a backup to be able to use Jenkins again.
[JENKINS-75237] Saving the security configuration form changes the Active Directory password in config.xml
Description |
Original:
When adding the groups on the Matrix based UI, the already encrypted password of the Jenkins config.xml was re-encrypted. As a result, the account could no longer connect to the domain and all users no longer had access to the Bronco. In addition, a port was added to the address.
We had to import a backup to be able to use jenkins again. |
New:
When adding the groups on the Matrix based UI, the already encrypted password of the Jenkins config.xml was re-encrypted. As a result, the account could no longer connect to the domain and all users no longer had access to the Jenkins Server. In addition, a port was added to the address.
We had to import a backup to be able to use jenkins again. |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Attachment | New: Bild (2).png [ 63913 ] |
When saving a configuration form, not just actual changes, but everything is saved. Based on the description, this looks like a problem in the unspecified security realm configuration form. Without more details, it's impossible to help you; it's however very unlikely that matrix-auth is the culprit, it's just what motivated you saving the configuration.
Given https://en.wikipedia.org/wiki/Bronco_(disambiguation) reveals no useful technology-related terms: Please note that you're reporting this issue to the Jenkins project. This is not an issue tracker internal to your organization.