Found the problem - FOSUserBundle changed ROLE_SUPERADMIN to ROLE_SUPER_ADMIN.
Changing it back to ROLE_SUPERADMIN in security.yml solved the problem, and we were able to get into the admin backend again. ... next step I guess is to drop and recreate the database using the latest FOSUserBundle, then reset the roles so they match up with the new security definition. Hopefully there are no other gotchas related to the new FOSUseBundle stuff. Fun! -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
