Probably caused by the fix for JENKINS-22769 in 1.584, so downgrading to 1.583 should be a viable workaround.
You should file a bug against createjobadvanced in Jira. On 23.10.2014, at 15:03, [email protected] wrote: > We do not want anonymous access to any job. > > Therefore we have set Authorization to 'Project based matrix Authorization > Strategy' and > allow Anonymous users only to 'Create Job' and 'Configure Job' > > The createprojectadvance plugin allowed to set 'Grant creator full control' > and a logged-in user used to be able to create a new Job, and he had directly > access to his Job. > > Since upgrade from Jenkins 1.563 to 1.584 this is no longer the case, after > creating a new Job the user will see: > Access Denied > Please login to access job renetest5 > > A user with Global Administrator permissions is able to open this new job and > it appears that > the user that has permissions is called 'SYSTEM', which is not a valid name. > > Upgrade of createprojectadvance plugin 1.1 to 1.2 makes no difference. > > Is there anyone who knows a solution? > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
