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.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Link||This issue is duplicated by SECURITY-1806 [ SECURITY-1806 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Remote Link||This issue links to "jenkins #4630 (Web Link)" [ 24824 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|