How to configure the users/roles for file-based authentication?

[awehrung]

I have been trying out Structurizr on premises and before deploying it somewhere I wanted to restrict workspace visibility. For testing, I am starting Structurizr on premises with Docker, creating a workspace with the admin API then importing a workspace.json file with the workspace API over Strucutrizr-CLI.

I am using the following properties:

# structurizr.properties
# enable admin api, key: "adminkey"
structurizr.apiKey=$2a$12$lz53Vskk66S.fjPZQUPXfujdCEnSuyEYqOnQosDQGXkklkqylEa1K
structurizr.admin=admin

# structurizr.users
# password==username
tester=$2a$12$mHewNvFzyJK77kZNkmynaurk1fTuSuPfR0CJhHzrJcx5cc1ymAGbK
user=$2a$12$p0rUBMpBixozFPa3wvMtg.5veuXWqjt0sFC1PSvfDStCObyPI55lq
admin=$2a$12$vcvMEVBKMlY4dYqfcMZsGeFi0ehJRoauDJzJj7jfA4CIGS1KebXKW
nobody=$2a$12$Ogv0GagD8rKnHOjtYc2gq.6TEFOSi8GpHY0MgGsrL1QA5aAWMZp.y

# structurizr.roles
tester=read
user=write
admin=write

Also, I have tried defining the roles within the Java spec:

WorkspaceConfiguration configuration = workspace.getConfiguration();
configuration.addUser("tester", Role.ReadOnly);
configuration.addUser("user", Role.ReadWrite);
configuration.addUser("admin", Role.ReadWrite);

When logged in with the admin user, I can see that the workspace is correctly imported and the user permissions are set. The "Public link" in the left side-bar is also gone. But I get an error when I click on the "Private link". In the container logs:

[WARN ] 2024-10-29 14:22:06.363 [http-nio-8080-exec-5] PageNotFound - No mapping for GET /api/workspace/1/branch/admin
[WARN ] 2024-10-29 14:22:06.363 [http-nio-8080-exec-5] PageNotFound - No endpoint GET /api/workspace/1/branch/admin.

If I remove the user config and make the workspace public again, the "Public link" works fine. Any idea what could cause this?

[awehrung]

Could this be a problem with the newest release version of the onpremises container (2024.06.25)? I am noticing that the controller organization has changed in the main branch, maybe this is a mismatch between UI (expecting the new routes) and the backend (serving the old routes). I will try other versions.

EDIT: it doesn't seem to work with the older versions either, which lets me think I am using this wrong. Could not test with the dev version yet.

[awehrung]

Looks like the problem is gone with version 2024.11.05 🙂