If your PostgreSQL server listens on a different port than the default port, you can append the port in the host tag, e.g. localhost:9586. Please make sure, that the database exists and the user has write access in this database (the user must be able to create new tables).

Central authentication (auth.oauth2.xml)

Your Samply.Auth instance needs an RSA private/public keypair in a format that Samply.Auth understands. Do not use a passphrase to protect the keys, otherwise Samply.Auth can not read them. Instead you should protect the configuration files itself, so that only the tomcat user can read the files. You are also strongly encouraged to not deploy other applications on the same Tomcat server as Samply.Auth.

The issuer value should be the base URL of your application. In case your private key got compromised, you can replace the private and public key, but you must also give your clients the new public key. In any case, the issuer value must not be changed.

Email (`auth.mail.xml)

Samply.Auth uses emails to send invite links, requests for email verification, requests for password resets, and other things. Those settings are configured via the auth.mail.xml file:

The host, protocol, port, user (optional, leave empty if not in use), password (optional, leave empty if not in use) values are used to create the connection to the SMTP server. The fromAddress is the email address that will be used to send emails.

The final templateFolder value points to a relative or absolute path on the hard drive, where all the email templates are stored. The email template files are SOY files, that you can customize to your needs. Use the default SOY files, if you do not want to customize the emails send by your Samply.Auth instance.

Deployment

Copy the war file into the webapps folder of your Tomcat installation and rename it according to your needs, e.g. ROOT.war.

See this website for more informations about context containers in tomcat.

Start the server.

Usage

Open your web browser and navigate to the application, e.g. $HOST/. The admin interface is available under the /admin/ path, e.g. $HOST/admin or http://localhost:8080/admin/.