|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I would consider a system property or similar to provide a temporary workaround to the probably small number of people already using the plugin who really need the current (insecure) behavior until something else if fixed or reconfigured. But I do not think it should be a UI option since it does not make sense going forward.