Chapter 3. User Web App

Table of Contents

3.1. Login
3.1.1. About
3.1.2. Select Language
3.1.3. Single Web App Session
3.1.4. Card Self Association Dialog
3.1.5. 2-Step Verification
3.2. Login Alternatives
3.3. SafePages
3.3.1. Document Expiration
3.3.2. Footer
3.3.3. Document Details
3.3.4. Browser
3.4. PDF
3.4.1. PDF Filters
3.4.2. Document Scope
3.4.3. Description
3.4.4. Security
3.4.5. Passwords
3.4.6. Letterhead
3.4.7. Download
3.4.8. Send
3.5. Print
3.5.1. Printer Selection
3.5.2. Printer Settings
3.5.3. Selected Printer
3.5.4. Delegated Print
3.5.5. Print Job Settings
3.5.6. Direct Print Release
3.5.7. Full Print Scope and Jobs
3.5.8. Delegated Print Edit
3.5.9. Job Ticket Print
3.6. Letterheads
3.7. Delete
3.8. Log
3.8.1. Documents
3.8.2. Transactions
3.9. Sort
3.10. User Details
3.10.1. Internet Printer
3.10.2. Telegram Configuration
3.10.3. Authentication
3.10.4. Pagometers
3.10.5. Financial
3.10.6. Redeem Voucher
3.10.7. Transfer Credit
3.10.8. Transfer Money
3.10.9. Send Bitcoins
3.11. Upload
3.11.1. Upload Dialog
3.12. Upload Drop Zone
3.13. GDPR Dialog

The User Web App can be reached at https://savapage:8632/. 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 21, Using an External Database.

3.1. Login

Web App: Login Dialog

Figure 3.1. Web App: Login Dialog


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.11.3, “User Authentication”.

Some invariants:

  • 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”.

  • When the system is in Maintenance Mode, access is restricted to users with Administrator role. Regular users are shown a message explaining the situation at this Login dialog, or after login in the authorized session.


You can use an alias as User Name. See Section 15.4, “User Name Aliases”.

3.1.1. About

The About dialog shows version and copyright information. The top of the dialog can be customized: see Section, “Custom HTML”.


The dialog contains a Printer Driver section with a download link for the CUPS SAVAPAGE.ppd file. This section can be enabled or disabled by setting the configuration key webapp.about.driver-download.enable to Y or N. See Section 4.11.14, “Config Editor” on how to change this value.

3.1.2. Select Language

Web App: Select Language Dialog

Figure 3.2. Web App: Select Language Dialog

  • 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.

  • Press Cancel to return to the login dialog.


You can use the webapp.language.available configuration property to enter a comma separated list of selectable ISO 639 language codes. For instance: de,en,fr,es,ru,nl. See Section 4.11.14, “Config Editor” on how to enter this value.

When the list is restricted to a single language, the Language button in is not shown in the Login dialog, and the Web App Locale is set to the single available language.

3.1.3. Single Web App Session

A warning message is shown when a desktop [11] 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.

Same type Web App session detected

Figure 3.3. Same type Web App session detected

When a user opens a second Web App session of another type this message is shown:

Web App type change detected

Figure 3.4. Web App type change detected

In both situations, either go back to the active Web App session or press Login to login to the intended Web App type. This will invalidate any other SavaPage session in the same browser instance.

3.1.4. Card Self Association Dialog

When an unknown card is swiped, and Card Self Association is enabled, the user is presented this dialog to associate the new card.

Web App: Login Dialog - Card Self Association

Figure 3.5. Web App: Login Dialog - Card Self Association

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 4.11.14, “Config Editor” on how to change this value.

3.1.5. 2-Step Verification

If a user enabled 2-Step Verification, they are prompted to enter their verification code, after a successful first login step.

Web App: Login Dialog - 2-Step Verification

Figure 3.6. Web App: Login Dialog - 2-Step Verification

Web App: Login Dialog - 2-Step Verification (recovery)

Figure 3.7. Web App: Login Dialog - 2-Step Verification (recovery)

[11] The Single Web App Session check is solely done for certain desktop browser sessions. Sessions on macOS and mobile devices are not checked.