What is stored
Users and permissions, access granting and review processes, configuration, historical and audit data.
Technology · for architects and administrators
sara.next is a web application in a classic layered model: a browser interface, a backend with business logic and a relational database. Sign-in is handled by an external identity provider.
High-level architecture
The frontend and backend are delivered as a single artefact. The components communicate over HTTPS and a REST API.
01 · User
HTTPS · redirect to sign-in
02 · sara.next application container
03 · Data and integrations
from the backend only
Illustrative diagram based on the architecture documentation.
Technology stack
A Java / Spring stack on the server side and Angular on the client side make it easier for architecture teams and IT audit to assess the solution.
| Area | Technology | Role |
|---|---|---|
| Frontend | Angular (SPA), TypeScript | The user interface; communicates only with the backend. |
| Backend | Java 17, Spring Boot | REST API, business logic, integrations, serving the frontend. |
| Data | Relational database, Hibernate / JPA | Application data, configuration, historical and audit data. |
| Security | Spring Security, SAML 2.0 | Sign-in through the identity provider, authorisation on the application side. |
| Integrations | REST, Microsoft Graph, OData, SQL | Data synchronisation and executing changes in target systems. |
| API documentation | OpenAPI | A description of the backend REST interfaces. |
| Getting started | Docker | One image: backend, frontend and the Java environment. |
Data
Users and permissions, access granting and review processes, configuration, historical and audit data.
Connection via JDBC. Microsoft SQL Server and PostgreSQL are supported.
Data changes are versioned, which makes it possible to analyse the history of record modifications.
Updated with migration scripts when a new version is deployed.
Integrations
All integrations are handled by the backend in dedicated components, separated from the business logic. Each application using auto-implementation has its own access token.
Integration models| Operation | Name | Scope |
|---|---|---|
| create | Creating access | Adding a user to a group, role, project, team or resource. |
| modify | Modifying access | Changing the scope, level or parameters of existing access. |
| swap | Change of user | Transferring access to another person, e.g. when covering for someone. |
| remove | Removing access | Revoking a membership, role or assignment. |
| verify | Execution verification | Checking whether the state in the application matches the decision. |
Next
A container in the cloud, in a Kubernetes cluster or on premises.
Resources, database, identity provider, network.
The SAML 2.0 sign-in flow step by step.
Authorisation, change control, monitoring.
Levels 0–5 and auto-implementation.
Configuring applications, roles and processes.
We will discuss the architecture, requirements and integration model for the applications you want to start with.