The plugin provides an Account component that is similiar to Rainlab.User's account component.

The Account component

The account component provides the main functionality and can be included in any CMS page that should serve as login endpoint.

The Account component has the following properties:

• model - [string] specifies the user model the form authenticates (must have an email field). Defaults to Rainlab\User\Models\User
• auth - [string] specifies a class of facade that manages the authentication state (see below). Defaults to Rainlab\User\Facades\Auth
• mail_template [string] the email template of the login mail. Defaults to nocio.passwordless::mail.login
• redirect [dropdown] specifies a page name to redirect to after sign in (can be overwritten, see below)
• allow_registration - [checkbox] if disabled, only existing users can request a login
• api - [checkbox] if enabled, the component will expose an API endpoint ?api to query the authentication status

The component will display the email login form and -- if the user is logged in -- display account information. Note that the component requires the ajax framework to work.

The authentication manager

The authentication manager that can be specified in the Account component is a class or facade that manages the user authentication through a standardised API:

• login($user) {} - signs in $user
• check() {} - checks whether user is authenticated (returns boolean)
• getUser() {} - returns the authenticated user or null if not authenticated
• logout() {} - logs the user out

Available auth managers:

Rainlab\User\Facades\Auth

Auth manager provided by the Rainlab.User plugin.

Nocio\Passwordless\Classes\CookieTokenAuth

Auth manager that stores authentication state as token in a httpOnly cookie. The user stays authenticated until the cookie is deleted or the token expires. The manager can be used as middleware to protect endpoints that require authentication. The authentication method is particuarly useful for RESTful APIs. Note that the cookie will only be transfered via secure https connections. If you want to allow http connections you can set COOKIE_TOKEN_SECURE=true in the .env file.

Custom manager

To cater for custom authentication mechanism you can implement your own auth manager that exhibits the given API. If you implemented an auth manager that could be useful to others please consider contributing it in a pull request.

Return redirections

The Account manager can process GET redirect requests after login, e.g. ?redirect=/awesome/redirect/url. This can be useful to improve the user expirience in the case in which an unauthenticated user accesses a page that requires authentication and is being redirected to the login page. Using GET, the original request location can be stored for after login so that the user is automatically redirected to the page she originally intended to access. Note that GET-redirects overwrite the redirection behaviour that can be defined in the component settings.

JSON API

If enabled, the Account component exposes and JSON API endpoint that can be consumed by an authenticated user (unauthenticated users will face an 401 Unauthorized. response). Currently, the only route is ?api=info which returns the jsonified user model.

Developer API

The plugin provides a token model Nocio\Passwordless\Models\Token that can be re-used by developers to implement token management. The model provides two main functions:

• generate($user, $expires = 10, $scope = 'default') which returns a token for a given $user model object (or more general the token payload). Make sure to specificy a custom scope, e.g. myplugin to avoid scope collision.
• parse($raw_token, $delete = false, $scope = null) which parses (and optionally $deletes) a provided $raw_token in a given $scope and returns the correspoding $user model. It raises an ApplicationException if the token is expired, invalid or cannot be parsed.

More details can be found in the model class documentation.

Support & Contribution

I can only offer limited support but will try to answer questions and feature requests on GitHub. I am also happy to accept pull requests, especially for the missing features list on the Plugin details page.