Setup
Setting up the dependencies, authentication and first administrator for a Stroom installation.
Once Stroom has been installed there are a number of things that need to be set up before it can be used. The order below is the one that most installations will want to follow.
- MySQL Setup - creating the database and the accounts Stroom uses to reach it.
- Processing Users - the operating system account that Stroom and Stroom-Proxy run as.
- Java Key Store Setup - the certificates used for secure communication.
- Open ID Connect - choosing and configuring the
Identity Provider (IDP)
Identity Provider (IDP)
An Identity Provider is a system or service that can authenticate a user and assert their identity. Identity providers can support single sign on (SSO), which allows the user to sign in once to the Identity Provider so they are then authenticated to all systems using that IDP.Click to see more details... that will authenticate your users.
- Creating the First Administrator - giving the new installation somebody who can log in and administer it.
- Securing Stroom - hardening the deployment.
- Email Setup - the SMTP server used by Analytic Rule and Report emails, only needed if you intend to use email.
Note
Creating the first administrator is easily missed.
A new installation normally has no administrator at all, so until that step is done nobody can log in and configure Stroom.
Securing Stroom
How to secure Stroom and the cluster
Creating the First Administrator
How to give a newly installed Stroom its first administrator, using the command line.
Email Setup
Configuring the SMTP server that Stroom uses to send Analytic Rule and Report emails.
Setting up Stroom with an Open ID Connect IDP
How to set up Stroom to authenticate users: with its own internal identity provider, with a 3rd party one such as KeyCloak, Cognito or Google, or behind an authenticating proxy such as an AWS Application Load Balancer.
Last modified October 20, 2026: Merge pull request #144 from gchq/add-7.14-rel-notes (2c6fb22)