How to Build a Mobile Application with Persistent Login

Description

Persistent login can be added to mobile applications, allowing users to log in to an application once and not requiring the user log in again, even if the application is closed.

Discussion

A common pattern in mobile applications is to not require the user to login to the application after they have successfully logged in for the first time. The login should be persistent until is is explicitly revoked by the action of an Administrator, or until the end of the persistent login period is reached.

The canAjaxCallback server-side event previously would only emit user-defined Javascript if the event denied permission for the callback. Now, user defined Javascript can be emitted even if the Ajax callback is allowed. This change was made to support the Mobile Application with Persistent Login pattern.

For more information on the approach used to implement this pattern, please view this document.

Mobile Applications with Persistent Logins

A common pattern in mobile applications is to not require the user to login to the application after they have successfully logged in for the first time. The login should be persistent until is is explicitly revoked by the action of an Administrator, or until the end of the persistent login period is reached.

Unlike a traditional Web application built using the Alpha Security Framework, the user will not have to log in again once their session expires, or when they restart the application.

In this video we show how this pattern is achieved.

Download Component

2017-04-29

See Also