After installation, you will be prompted to open a web browser at
https://
to complete the configuration. The configuration steps are explained below.savapage:8632/admin
Login with username
admin. This is the built-in administration account. Enter
admin as password. This is the standard password as set
by the installer.
After login the Dashboard is shown where you will notice the system status “Setup is needed”. The next steps guide you in configuring the system so that the status will change to “Ready to use”.
As long as system setup is needed login attempts at the User Web App are blocked with a message saying “Application setup is required”.
As a first security measure change the master password for the built-in
admin account. This account is independent and not
related to the operating system or domain. The password needs to meet minimum
strength requirements, and must contain at least six characters. Select
→ → , enter and confirm the new password and press the
button.
Make sure that this password is kept at a secure place since it is the key to your system.
More information about the admin password can be found in Section 17.1.1.3, “Internal Admin Password”.
Set the system's locale; ensure that these are correct before proceeding.
Select → → , and enter the locale string. Some examples are:
en, en-GB, en-US, nl,
nl-NL, nl-BE. You can leave the locale empty to
accept the system default. The locale is applied to all system messages which
are logged in the system log or send by email. See Section 19.1, “Localization”.
Set the system's currency code; ensure that these are correct before
proceeding. Select → , and enter the ISO 4217 Currency code. Some examples
are: USD, EUR, GBP. The currency
symbol is determined in the context of the user or
system locale. See Section 19.1, “Localization”.
SavaPage optionally imports user information from a Unix (PAM, NIS, etc.) or LDAP source.
Select → .
Select Unix if the user accounts are setup
and defined on the local system as standard Unix accounts or mapped into the
system from a central directory service such as LDAP via
nsswitch.conf and PAM. Most large
established networks will use this option.
For administrators wishing to customize the PAM authentication method at the application level, SavaPage reports itself as “savapage”.
The LDAP option is appropriate for large networks with existing LDAP domains. This includes networks running OpenLDAP, FreeIPA, Apple Open Directory, Novell eDirectory, Microsoft Active Directory and Google Cloud Directory.
More information on LDAP is available in Section 4.11.1.2, “LDAP”.
After selecting the source, enter the necessary parameters (LDAP only) and press the button.
Skip this step if you did not set an external User Source in the previous step. Otherwise, select → → → to import users.
An option exists to import a subset of users from the source by selecting a group. This option is relevant if only a subset of users will ever use SavaPage. Select → → to select the group.
Test the import first by pushing the button. A simulated import will start, with each step echoed below the button, so you can verify the effect of your action.
Select → , enter the SMTP and Message options and press the button. Data from the Messages section is used for system generated mail messages.
You can send a test mail message to a recipient of your choice by pressing the button after you applied the changes.
Mail Print and Web Print are disabled by default. You can enable and configure these options at → and → .
If you enabled one of these Driverless File Transfer Print options, decide which PDF converters you want to enable at → → . Beware that you might need to install the converter software on the SavaPage host.