Authentication and Authorization

Different web applications will employ different authorization and authentication strategies. In some cases, access to the entire application is restricted unless the user enters a password. In other cases, the users can access most of the functions in the application, however gain additional functionality if authenticated.

Agile Toolkit provides a basic authentication mechanism, with support for white-list and black-list strategies.


Using The BasicAuth Class

The BasicAuth controller is a simple implementation of the Authentication class. Below is an example of usage from inside the API class:


The above code will add BasicAuth into the API, manually allow 2 users to have access, then perform the check. You will see a login form when accessing any page handled by this API. Class SQLAuth can be used if you wish to authenticate users against the database.


Implementing White-List

Both black-list and white-list implementation depend on executing - or bypassing - the "check" method. In a white-list implementation, if check() is not executed, then authentication is not required. You can use allowPage() to specify which pages do not need authentication, and then use isPageAllowed() to determine when to perform the check(). Note that if the user is logged in, even without having explicitly called check() - ie., when visiting an allowed page - their login information will be available.

$this->add('BasicAuth');     // automatically sets $api->auth to self

Implementing black-list

To keep non-authenticated users away from certain pages you should move the call to $api->check() to inside those pages.

// inside page/secret.php, in page's init() method

$this->add('Text')->set('Hello, ',$this->api->auth->model['name']);

Creating your custom authentication page

Altirnative validation ways (such as open-id)