After installation, you will be prompted to open a web browser at
to complete the configuration. The configuration steps are explained below.
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 188.8.131.52, “Internal Admin Password”.
Set the system's locale; ensure that these are correct before proceeding.
Select , and enter the locale string. Some examples are:
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 17.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
GBP. The currency
symbol is determined in the context of the user or
system locale. See Section 17.1, “Localization”.
SavaPage optionally imports user information from a Unix (PAM, NIS, etc.) or LDAP source.
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, Apple Open Directory, Novell eDirectory and Microsoft Active Directory.
More information on LDAP is available in Section 184.108.40.206, “LDAP”.
After selecting the source, enter the necessary parameters (LDAP only) and press thebutton.
Test the import first by pushing thebutton. A simulated import will start, with each step echoed below the button, so you can verify the effect of your action.
You can send a test mail message to a recipient of your choice by pressing thebutton after you applied the changes.