|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Is this actually about github-oauth? Looks more like a core issue to me...
That being said, this is a horrible idea, and here's why:
The sensible approach is to implement UnprotectedRootAction in plugins where the authors considers the security implementations.
FWIW a plugin could probably manage to add this functionality by acting as an internal proxy of sorts (Build Token Root plugin on steroids). But this should never be part of the default configuration, and should have come with warnings regarding its use (similar to Anything Goes Markup Formatter).