Documentation Gaps about authentication HOT 10 CLOSED

We need a tutorial app :)

from authentication.

All actions are public and stay public, authentication has nothing to do with that. It just gives you an identity if an user is logged in. You can implement a check based on that in isAuthorized() for example using the still existing and useable old authorization system.

from authentication.

Refs #69

from authentication.

@HaroldPutman This pluginonly handles authentication, not authorization.

If you want to build a basic login page, refer to the AuthenticationComponent. You have different options for that, depending which Authenticator you want to use.

from authentication.

@cleptric I think @HaroldPutman is looking for an example of the more common authenticators 😄

from authentication.

Can we close this ticket? 2) Should be pretty clear now right on the readme.md 1) and 3) should be covered in the docs and / or a separate tutorial should be created.

from authentication.

I would keep the ticket open until someone gets around to writing the tutorial.

from authentication.

Let's create a more specific ticket then with the exact requirements of what needs to be done and just link this here.

from authentication.

I'm cool with closing this issue. The recently added notes in the documentation help answer my original question.

from authentication.

Hold on... I think Auth->allow() is not for authorization but for disabling authentication for controllers or actions. I'm afraid currently all requests must be authenticated. Is there a way to make an action "public"?

from authentication.