Appearance
Configuration
Squizy is configured through properties under the squizy.* prefix in your application.properties or application.yml. Standard Spring Boot properties (datasource, JPA, etc.) follow their usual Spring documentation.
Server (squizy.server.*)
General server-level settings.
| Property | Description | Default |
|---|---|---|
squizy.server.return-stack-trace | Return full stack traces to the client in error responses. Enable only for debugging. | false |
squizy.server.exception-handler-order | Order of the Squizy exception handler. Adjust to integrate with other exception handlers. | 100 |
squizy.server.default-composite-id-separator | URL separator for composite keys (e.g., /api/entity/key1___key2) | ___ |
squizy.server.logging-ignored-paths | Paths excluded from the Squizy logging filter | /actuator/health, /actuator/prometheus |
Client (squizy.client.*)
Settings for the frontend client connection.
| Property | Description | Default |
|---|---|---|
squizy.client.client-url | URL of the frontend client. Required when running the frontend separately. | (empty — same origin) |
CORS (squizy.cors.*)
Cross-Origin Resource Sharing configuration. Only needed when the frontend runs on a different origin than the backend.
| Property | Description | Default |
|---|---|---|
squizy.cors.allow-credentials | Allow credentials (cookies) in cross-origin requests | true |
squizy.cors.allowed-origins | List of allowed origins | (none) |
squizy.cors.allowed-headers | List of allowed headers | * |
squizy.cors.allowed-methods | List of allowed HTTP methods | * |
Example for separate frontend deployment:
properties
squizy.client.client-url=https://app.example.com
squizy.cors.allowed-origins=https://app.example.comLogging (squizy.logging.*)
Structured HTTP request/response logging. See Logging for details.
| Property | Description | Default |
|---|---|---|
squizy.logging.default-logged-actions | Actions logged at INFO level for all entities. Values: READ, CREATE, UPDATE, DELETE | (none — all at DEBUG) |
squizy.logging.entity-logged-actions.{entity} | Per-entity override of logged actions | Falls back to default |
Authentication
Authentication provider configuration depends on which provider you are using. Each provider has its own set of properties:
- OAuth2 —
squizy.oauth2.*properties for token management, cookie settings, and OAuth2 flow configuration