Skip to content
Documentation

Security Configuration

Security in PowerTSM consists of two independently configured subsystems. Both are selected from configuration at runtime, so the mechanism can be changed without modifying application code.

HAKOM:Security
Security
├─ Authentication
│ ├─ DefaultIdentityProvider
│ ├─ IdentifierClaimType
│ └─ IdentityProviders
└─ Authorization
├─ DefaultAuthorizationService
└─ AuthorizationServices

Authentication establishes who is making a request. An identity provider validates whatever proof the request carries: a JWT, a session cookie, the Windows account of the process, or a fixed identity from the configuration and produces a set of claims describing the user. If no valid proof is present, the request fails with HTTP 401.

Authorization decides what that user may do. An authorization service evaluates the claims against rules attached to the resource being accessed and grants or denies the requested permissions. A request that is denied fails with HTTP 403.

Authentication always runs first, and its result is the input to authorization:

Request ──► Authentication ──► claims ──► Authorization ──► allowed / 403
│
└──► no valid identity ──► 401

The two are configured separately and neither implies the other. A successfully authenticated user may hold no permissions at all.

The output of authentication is a set of claims. These are statements about the user, each with a type and a value, such as sub (a stable unique identifier), name, email, or group and role memberships. Claims come from the identity provider; PowerTSM does not maintain its own user accounts or passwords.

Claim types are not standardized across identity providers, and the same provider may name or supply them differently depending on how it is configured. Three settings control how the incoming claims are interpreted:

  • IdentifierClaimType — the claim that uniquely identifies the user (default sub).
  • NameClaimType — the claim that supplies the identity’s primary name.
  • RoleClaimType — the claim that carries the identity’s roles.

In addition, ClaimTransformations can rename or map incoming claims before they are evaluated. See Authentication Configuration for details.

The PowerTSM HTTP API exposes GET /identity, which returns the identity resulting from the current request containing all claims after transformation, together with the effective name and role claim types. This is the fastest way to confirm that authentication works and that claims arrive under the expected names. GET /identityProviders lists the providers that were configured successfully.

© 2026 Volue.Version v0.6.38017 November 2026