After a clean install of AppBoard using the default configuration the following details will bring up the login screen, and after logging in, will then bring up the AppBoard Builder. Please note all login page fields are case sensitive.
The table below summarizes the important URLs for accessing AppBoard.
The dispatcher provides a way to bypass the login screen and pass login credentials via URL parameters. It can also be used to redirect to a different URL once logged in.
The default home is used to determine what URL to send a User to when a full path is not provided in the URL, or in cases such as when a User switches to a different Role. By default AppBoard is configured to have itself as the home URL, but in some cases where enPortal is the main interface for end-users then enPortal can be configured as the home URL.
To override the default configuration, and have enPortal as the default home:
The following parameters can be used to automatically authenticate:
By default it is possible to authenticate using both GET and POST requests. It is recommended to use the POST method as this avoids credentials being logged in the access log. In some environments it may be necessary to completely prevent GET logins, this can be done by editing [INSTALL_HOME]/server/webapps/enportal/WEB-INF/config/custom.properties and adding the line dispatch.loginPostOnly=true. A server restart is required after making this change.
To redirect to a specific URL after authenticating use the redirect URL parameter.
By default the stack order and set of stacks is controlled by provisioning stacks to roles. However, it’s also possible further restrict the list of visible stacks and select a specific stack by using the following URL parameters. Please note this does not grant permissions, the user/role must already have permission to view the stacks.
A typical use case here is to combine passing in authentication credentials with a specific stack selected for use on an unattended wall display.
Determining the stack ID can be done from the Builder interface using the Diagnostics tool available in the header next to the help menu. Select the Data button and navigate to appboard.config.Stack. Expand out each item to see the stack title and record the IDs for the stack(s) you’re interested in.
Kiosk mode is useful for unattended displays to cycle through a set of stacks automatically, and auto-extend the session to prevent the client from logging out. In addition kiosk mode can be combined with other dispatcher options such as the Stacks options to further restrict the set of stacks or change from the default display mode to Button mode. Supported options are:
Additional session variables can be passed in via URL parameter to AppBoard and utilized using SHIM expressions. Only defined variables that are not marked Server Use Only will be passed through. Refer to the Session Variables documentation for more information on creating and using these.