Daniel, Okay, that makes sense. Unfortunately, that leaves me completely stumped as to why it's ending up configured to use hudson.security.HudsonPrivateSecurityRealm when I run it in EC2. Historically speaking, it's likely that I'm doing something stupid that gets it into that state, except... I can't see what that might be.
Any chance there's some weird race condition, where the initial config transitions from one state to another -- and mine's just getting stuck with the one? Confusedly yours, Karl M. Davis On Sunday, October 8, 2017 at 11:27:38 AM UTC-4, Daniel Beck wrote: > > > > On 8. Oct 2017, at 17:20, Karl Davis <[email protected] > <javascript:>> wrote: > > > > Shouldn't a clean install of Jenkins end up configured to use > hudson.security.HudsonPrivateSecurityRealm? > > Not if you explicitly disable the setup wizard (then you're expected to > set things up yourself from scratch). The behavior is as documented on > https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b75cb573-6c9f-4f0a-ae68-0e38d9db96eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
