Code Iginter Core subclassing

[eluser]Colin Williams[/eluser]

so far, this is the classic problem on user authentication

It's not a classic problem, it's your app's problem. There are many ways you can make something happen all the time. One way is to use a hook. Another way is to autoload a library and do the authentication/authorization check in its constructor. Yet another way is to have an extra parent controller that the rest of your controllers extend.

And remember, there will be a few pages that you don't want locked out, notably the login page and perhaps a "forgot password" page.

If you really just need to lock down an entire app and don't need role- or group-based permissions, look into using your servers authentication/authorization modules