On-premises installation
Overview | Software architecture | Download | Deployment | Configuration | Troubleshooting | FAQ | EULAAuthentication | LDAP | SAML 2.0 | Authorisation and role-based access | HTTPS | Amazon Web Services S3 | Elasticsearch
Authentication
There are three variants of the on-premises installation, each with different authentication methods:
- Form-based login, with a file-based user store (as described on this page)
- Form-based login, with integration to your LDAP server
- Single sign-on with your Identity Provider via SAML 2.0
Form-based login, with a file-based user store
This variant is included with the basic installation, and configured to use a form-based login (username and password), with the set of users stored in a file called
structurizr.users
in the Structurizr data directory (passwords are hashed using bcrypt).
A user with the username of structurizr
and password of password
is created by default.
You can add, remove or modify users as needed. Each line in this file should be in the following format:
{username}={hashed password}
A simple utility page is provided to calculate a bcrypt hashed password at {structurizr.url}/bcrypt/{password}
(e.g. http://localhost:8080/bcrypt/password).
It is also possible to configure a comma separated list of roles for every user, in a file called structurizr.roles
, again in the Structurizr data directory.
Each line in this file should be in the following format:
{username}={role1},{role2},{role3}