Forgot to add the following in the backend settings.yml
login_module: sfGuardAuth
login_action: signin
secure_module: sfGuardAuth
secure_action: secure
So for anyone stuck with this the solution was either, add this AND
sfGuardAuth in the settings (which I'm pretty sure I did before)
OR the above AND creating the admin user.
Thanks for the help Gábor and safa.
On Apr 23, 3:12 pm, Gábor Fási <maerl...@gmail.com> wrote:
> sfGuardAuth is the module that handles the authentication and
> authorization, you'll need to enable that as well. The other modules
> are to manage the users, the permissions, etc.
>
>
>
> On Fri, Apr 23, 2010 at 15:56, Tofuwarrior <p...@clearintent.co.uk> wrote:
> > Hi,
>
> > I've followed through the sfGuard installation and have used it fine
> > for the front end.
>
> > Now I have enabled it in the backend and set
> > default:
> > is_secure: true
>
> > in the backend but it displays a page saying this page is not public
> > and saying I need to login in the login form This isn't displayed, it
> > just links to the same page (/default/login)
>
> > I've trawled around and it seems that this is a common issue over the
> > years but for different reasons and none of them are my reason by the
> > look of it.
>
> > I am expecting sfGuard to do the same as frontend - ie show me a login
> > form so my first question is, is this how it should work?
>
> > I am presuming it is. So now I am stumped, I have enabled the
> > following as per the instructions.
>
> > backend/../settings.yml
> > all:
> > enabled_modules: [default, sfGuardGroup, sfGuardPermission,
> > sfGuardUser]
>
> > I've done ./symfony cc
> > I've done propel:build-all-load
>
> > Then the instructions talk about the front end application so I didn't
> > do that stuff because it is referring to sfGuardAuth which the guide
> > explcitly says is only needed for the frontend.
>
> > This seems a bit wierd - what does the authentication for the backend
> > then. I feel like I am missing something fundamental about how this
> > happens, should I redirect backend authentication to the frontend or
> > something? That just doesn't seem to make sense.
>
> > I'm lost! Anyone help.
> > I've looked at the extended sfGuardDocs in the wiki as well as stuff
> > on the forum and web generally.
>
> > Thanks,
>
> > Paul
>
> > --
> > 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
>
> --
> 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
> athttp://groups.google.com/group/symfony-users?hl=en
--
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
