Hello Daniel, I've solved it somehow. I did find a XML conf file. There I did change some false/true-settings. In the end the Jenkins was open for write by everybody (also unknown user).
Then I could remove user admin and add a new one with defined pw. I also created a "work-"account. Then I did set back the openness. Thanks so far, best regards, Thomas On Monday, April 30, 2018 at 4:20:10 PM UTC+2, Daniel Beck wrote: > > > > On 30. Apr 2018, at 10:39, Thomas Hofmann <[email protected] > <javascript:>> wrote: > > > > java -jar c:\temp\Software\Online\Jenkins\jenkins.war --httpPort=9090 > --argumentsRealm.roles.toohoo=admin --argumentsR > > ealm.passwd.toohoo=XXXXXXXXXX > --logfile=c:\temp\jenkins\logs/winstone_date-20180430-103646.log > > Jenkins has built in security realms with default authentication that are > independent of the container's security. So if you see a friendly > butler-themed login page, these are not the credentials to use. > > Check secrets/initialAdminPassword in JENKINS_HOME, if that exists try > user 'admin' and that password. > > -- 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/7740ad0e-0a8f-4e2a-8bb6-e15451f703f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
