|
||||||||||||||
|
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.
The useSecurity field is obsolete as indicated by its Javadoc. It's left in for backwards compatibility.
You cannot just "enable security", as you'll need to define security realm and authorization strategy to use, both of which have setters (one of which you use with null argument resulting in "no security" fallback).
I really don't see the issue here. The useSecurity flag is internal API only, and not exposed as public API. The getter isUseSecurity works completely independent of that field (since the field is obsolete).