Login Screenlet for Android


  • Android SDK 4.1 (API Level 16) or above
  • Liferay Portal 6.2 CE/EE, Liferay CE Portal 7.0/7.1, Liferay DXP 7.0+


  • Android SDK 4.1 (API Level 16) or above

Xamarin Requirements

  • Visual Studio 7.2
  • Mono .NET framework


Login Screenlet lets you authenticate portal users in your Android app. The following types of authentication are supported:

  • Basic: uses user login and password according to HTTP Basic Access Authentication specification. Depending on the authentication method used by your Liferay instance, you need to provide the user’s email address, screen name, or user ID. You also need to provide the user’s password.

  • OAuth: implements the OAuth 1.0a specification.

  • Cookie: uses a cookie to log in. This lets you access documents and images in the portal’s document library without the guest view permission in the portal. The other authentication types require this permission to access such files.

For instructions on configuring the Screenlet to use these authentication types, see the below Portal Configuration and Screenlet Attributes sections.

When a user successfully authenticates, their user attributes are retrieved for use in the app. You can use the SessionContext class to get the current user’s attributes.

Note that user credentials and attributes can be stored in an app’s data store (see the saveCredentials attribute). Android’s SharedPreferences is currently the only data store implemented. However, new and more secure data stores will be added in the future. Stored user credentials can be used to automatically log the user in to subsequent sessions. To do this, you can use the method SessionContext.loadStoredCredentials().

JSON Services Used

Screenlets in Liferay Screens call the portal’s JSON web services. This Screenlet calls the following services and methods.

UserServicegetUserByEmailAddressBasic login
UserServicegetUserByScreenNameBasic login
UserServicegetUserByIdBasic login
UserServicegetCurrentUserCookie and OAuth login


  • Auth


  • Default
  • Material

For instructions on using these Views, see the layoutId attribute in the Attributes section below.

The Login Screenlet using the Default (left) and Material (right) Viewsets.

Portal Configuration

Basic Authentication

Before using Login Screenlet, you should make sure your portal is configured with the authentication option you want to use. You can choose email address, screen name, or user ID. You can set this in the Control Panel by selecting ConfigurationInstance Settings, and then selecting the Authentication section. The authentication options are in the How do users authenticate? selector menu.

Setting the authentication method in your Liferay instance.

For more details, see the Setting up a Liferay Instance section of the User Guide.

OAuth Authentication

To use OAuth authentication, first install the OAuth provider app from the Liferay Marketplace. Click here to get this app. Once it’s installed, go to Control PanelUsersOAuth Admin, and add a new application to be used from Liferay Screens. Once the application exists, copy the Consumer Key and Consumer Secret values for later use in Login Screenlet.


This Screenlet doesn’t support offline mode. It requires network connectivity. If you need to log in users automatically, even when there’s no network connection, you can use the credentialsStorage attribute together with the SessionContext.loadStoredCredentials method.

Required Attributes

  • None


AttributeData typeExplanation
layoutId@layoutThe ID of the View’s layout. You can set this attribute to @layout/login_default (Default View) or @layout/login_material (Material View). To use the Material View, you must first install the Material View Set. Click here for instructions on installing and using Views and View Sets, including the Material View Set.
companyIdnumberThe ID of the portal instance to authenticate to. If you don’t set this attribute or set it to 0, the Screenlet uses the companyId setting in LiferayServerContext.
loginModeenumThe Screenlet’s authentication type. You can set this attribute to basic, oauth, or cookie. If you don’t set this attribute, the Screenlet defaults to basic authentication.
basicAuthMethodstringSpecifies the authentication option to use with basic or cookie authentication. You can set this attribute to email, screenName or userId. This must match the server’s authentication option. If you don’t set this attribute, and don’t set the loginMode attribute to oauth, the Screenlet defaults to basic authentication with the email option.
OAuthConsumerKeystringSpecifies the Consumer Key to use in OAuth authentication.
OAuthConsumerSecretstringSpecifies the Consumer Secret to use in OAuth authentication.
credentialsStorageenumSets the mode for storing user credentials. The possible values are none, auto, and shared_preferences. If set to shared_preferences, the user credentials and attributes are stored using Android’s SharedPreferences class. If set to none, user credentials and attributes aren’t saved at all. If set to auto, the best of the available storage modes is used. Currently, this is equivalent to shared_preferences. The default value is none.
shouldHandleCookieExpirationbool Whether to refresh the cookie automatically when using cookie login. When set to true (the default value), the cookie refreshes as it’s about to expire.
cookieExpirationTimeint How long the cookie lasts, in seconds. This value depends on your portal instance’s configuration. The default value is 900.
authenticatorAuthenticator An instance of a class that implements the Authenticator interface. The Challenge-Response Authentication section below discusses this further.


The Login Screenlet delegates some events to an object that implements the LoginListener interface. This interface let you implement the following methods:

  • onLoginSuccess(User user): Called when login successfully completes. The user parameter contains a set of the logged in user’s attributes. The supported keys are the same as those in the portal’s User entity.

  • onLoginFailure(Exception e): Called when an error occurs in the process.

Challenge-Response Authentication

To support challenge-response authentication when using a cookie to log in to the portal, Login Screenlet has an authenticator attribute. As mentioned in the above Attributes table, this attribute’s value is a class that implements the Authenticator interface.

Here’s an example of such a class. It sends a basic authorization in response to an authentication challenge:

public class BasicAuthAutenticator extends BasicAuthentication implements Authenticator {

    public BasicAuthAutenticator(String username, String password) {
        super(username, password);

    public Request authenticate(Proxy proxy, Response response) throws IOException {
        String credential = Credentials.basic(username, password);
        return response.request().newBuilder().header(Headers.AUTHORIZATION, credential).build();

    public Request authenticateProxy(Proxy proxy, Response response) throws IOException {
        return null;
« Introduction to Screenlets in Liferay Screens for AndroidSign Up Screenlet for Android »
Was this article helpful?
0 out of 0 found this helpful