Use newer jelly tag for direct keys about google-oauth-plugin HOT 7 OPEN

@Casz Thanks for pointing this out. Is this a situation where it would be appropriate to blacklist the 0.8 release after releasing this fix?

from google-oauth-plugin.

it could be: see jenkins-infra/update-center2#263 for an example of this 😓

from google-oauth-plugin.

Can you explain the utility/security that this provides over an invisible entry? We already don't render these keys, and it is still possible to view the encoded secret with secretTextarea through inspect element.

from google-oauth-plugin.

The one use I could see would be directly inputting a secret without uploading a file

from google-oauth-plugin.

Ya, it is meant for direct key entries, sorry if that wasn't clear 👍

from google-oauth-plugin.

See screenshots at jenkinsci/jenkins#3967

from google-oauth-plugin.

Thanks for clarifying, I'm glad this is a feature request and not a security concern.

Support for direct input would be interesting, although I think it might require more thinking into how to integrate that with the existing file upload UI elements.

from google-oauth-plugin.