Once Curity has been installed, it is time to configure it for the first time. This tutorial will setup the basic configuration so that the following is running:
- An Authentication service
- A token service for OAuth and OpenID Connect
- A User Management Service for SCIM 2.0
We'll setup the HSQL Database, which is a file based database that cannot be used in production but is contained in the installation.
Admin UI Overview
Login to the Admin UI at https://localhost:6749/admin (or the host where the machine is deployed).
Enter the username
admin and the password you set during the installation.
The main screen is structured as follows:
- The sidebar will change depending on what section is visited
- The profiles, these define the server functions
- Changes menu, here the configuration changes are applied, viewed or cancelled.
- The User menu, manage admin users.
- Facilities, here all helper services are defined, such as data sources, certificates and emails services
Setup a data-source
Firstly, we'll setup a data source. Curity comes with a predefined HSQL datasource that can be used when working with a development instance.
- Click the Facilities button to the right and click "New" in the data-source section.
- Give it a name (eg. 'main-ds') and click create.
Now you can configure a datasouce, we will setup HSQL which is a jdbc data-source.
The following should be entered:
- Connection String:
org.hsqldb.jdbc.JDBCDriver(available in a dropdown)
Then click Close in the bottom of the modal.
Commit the first change
Whenever changes are made in the UI they are not deployed to the server until the admin commits them. They are kept in a transaction, that will be validated when committed. This ensures that all new configuration states are correct and that no config is invalid.
To commit a change simply select Commit from the Changes menu:
You will be prompted for a comment. This is optional but useful if you want to rollback later.
Add a comment if you like, and then click OK.
All changes are now applied.
Setup a runtime node
In order to use Curity, we need at least one runtime node configured. We can use the admin node as both runtime and admin, but creating a service with the same name as the admin node.
- Go to Deployments and click New Server
- Give it the name
adminand click Create
Note: The name of the server should match the
-sparameter used when starting Curity. In a default installation this is
default-admin-ssl-key for now as the SSL certificate for the admin node. This can and should be changed later.
Close the dialog and commit the changes using the changes menu as before.
Now you should see a new node called
admin in the list of servers.