Customizing the Login Page
The login page can be customized for Web, Tablet, Phone and Electron Apps.
For Desktop Apps, see Command Line Switches.
The default login.rsp and login_recaptcha.rsp (run when reCAPTCHA is enabled) files for Web Apps reside in:
Prior to v6.0:
The default file is specified in the HTTP Settings in the Server Manager on Windows or in the environment variable DB_WWWDEFAULT on Linux and macOS.
You can customize your own by copying the default files and editing them to brand them.
The default login_phone.html and login_tablet.html files used for mobile Apps reside in:
Prior to v6.0:
When generating code for the mobile App, if these files exist in the app directory they will be used instead. You can customize your own by copying the default files and editing them to brand them.
The default login_web.html and login_web_recaptcha.html files used by Electron reside in:
Prior to v6.0:
When generating code for the Electron App, if these files exist in the app directory they will be used instead. You can customize your own by copying the default files and editing them to brand them.
Google reCAPTCHA is displayed on the Web login page if enabled in the Lianja Server.
The reCAPTCHA can be enabled or disabled in the Security Settings in the Server Manager on Windows or by setting the environment variable DB_WWWRECAPTCHA on Linux and macOS.
Authenticating and Bypassing the App Center
There are occasions that you want to login and run an App directly without having to go through the App Center.
For example, put this in the browser address bar (or an href in a link).
or login, run an App and go to a specific page.
This enhancement provides the ability to use the reCAPTCHA login page to authenticate, setup the correct roles and permissions and then navigate to the specified app.
You can also authenticate and run a .rsp page. For example, where myreport.rsp resides in the library directory:
You can pass arguments like this:
loginappFrom v9.0, including the loginapp=<appname> value pair in the roles list for a user will open the App specified in <appname> when that user logs in instead of displaying the App Center, e.g.
Customizing using the tenant_config.js file
From v5.2 the tenant_config.js file can also be used to customize the appearance of the login and App Center pages. It can include customizations such as the header icon and text, background images and captions.
An example file is included in the distribution as _tenant_config.js - just remove the leading '_' to test its effects.
One-Time Passcode Two Factor Authentication
From v8.0, two factor authentication (2FA) is supported for the Lianja Cloud / Lianja Cloud Server via the sending of a one-time passcode (OTP).
To enable 2FA on the server, check the 'Enable 2FA' box in the Lianja Server Manager Security tab on Windows or set the environment variable DB_2FA_ENABLED to 'true' on Linux or macOS.
When a user logs in, if they have an email address specified in their user record, they will be sent 6-digit OTP to complete their login. If the user record contains more than one email address, the OTP will be sent to all the email addresses.
The OTP is valid for five minutes and must be entered on the login page.