Too many people get theĀ Secret getters wrong. What if we just always returned a Secret, and had a StringConverter to handle submitted secrets and transparently decrypt again?
This would eliminate this class of problem. Only storage would really need to be done as Secret, but the internal API types wouldn't matter so much.
Test cases need to include String typed encrypted secrets, and unmatched getter/setter types.
- causes
-
JENKINS-63500 JENKINS-61808 breaks doc generation for build and input steps
- Open
-
JENKINS-63499 Configuration of password parameters broken in Declarative Pipelines in Jenkins 2.236+
- Resolved
-
JENKINS-62305 Error "hudson.model.PasswordParameterValue.value expects class hudson.util.Secret" since 2.236
- Resolved
-
JENKINS-63516 Use of password parameters with the input step broken in Jenkins 2.236+
- Resolved
- links to