Always encrypt f:password values, not just those backed by Secret

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 2.236

      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.

            Assignee:
            Daniel Beck
            Reporter:
            Daniel Beck
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: