Table of Contents
The User Web App can be reached at
For all URL options see Appendix E, URL Cheat Sheet.
When using the User Web App concurrently with the User Client and Proxy Print Authentication you are strongly advised to use an external database like PostgreSQL. See Chapter 18, Using an External Database.
When a user opens the Web App the login dialog is skipped when an Authentication Token is present in local storage of the browser. The login dialog is also skipped when the Web App is opened from a trusted and authenticated User Client or with a One-Time Authentication Token.
For a description of the global user authentication defaults see Section 4.10.3, “User Authentication”.
The language of the dialog defaults to the language setting of the browser.
You can overrule the default language and country or preselect a user by using the URL parameters. See Appendix E, URL Cheat Sheet
Version and copyright information is shown when you press the Section 3.1.1, “About”.button. See
You can choose an alternative language by pressing the Section 3.1.2, “Select Language”.button. See
The top of the Login dialog can be customized: see Section 22.214.171.124, “Custom HTML”.
Login Alternatives appear at the bottom of the dialog.
Only Persons can login.
Disabled users are not allowed to log in.
The internal "admin" user is not allowed to log in as user.
As long as system setup is needed user login attempts are blocked with a message saying “Application setup is required”.
You can use an alias as User Name. See Section 12.4, “User Name Aliases”.
The About dialog shows version and copyright information. The top of the dialog can be customized: see Section 126.96.36.199, “Custom HTML”.
At the moment English, German and Dutch are fully supported. Press the language of your choice. This will reload the login dialog in the newly selected language.
Pressto return to the login dialog.
You can use the
configuration property to enter a comma separated list of selectable ISO
639 language codes. For instance:
See Section 188.8.131.52, “Config Editor” on
how to enter this value.
When the list is restricted to a single language, the Login dialog, and the Web App Locale is set to the single available language.button in is not shown in the
A warning message is shown when a desktop  user tries to open the same Web App type a second time in the same browser instance. In rare occasions, for instance, due to network connectivity issues, this statement might be false. In that case a Login will bring you back on track.
When a user opens a second Web App session of another type this message is shown:
In both situations, either go back to the active Web App session or pressto login to the intended Web App type. This will invalidate any other SavaPage session in the same browser instance.
The appearance of the Login dialog on a device depends on the following settings:
Terminal settings overrule global settings, and the URL parameter overrules the defined default. When available, alternative login methods can be selected by tapping the method button at the bottom of the dialog. Some sample Login dialogs are shown below.
A special URL path is available to use OAuth as SSO for User Web App. This URL can be presented on the site of an OAuth provider, to seamlessly link to SavaPage. See Appendix E, URL Cheat Sheet.
When an unknown card is swiped, and Card Self Association is enabled, the user is presented this dialog to associate the new card.
There is a time limit to enter the Username and Password. The remaining
seconds are shown and when counted down to zero the dialog is automatically
closed. The time limit (seconds) is contained in configuration key
webapp.card-assoc.dialog-max-secs. See Section 184.108.40.206, “Config Editor” on how to change
 The Single Web App Session check is solely done for certain desktop browser sessions. Sessions on macOS and mobile devices are not checked.