Identity Governance & Administration
sara.next
  1. sara.next
  2. Technology
  3. Architecture

Technology · for architects and administrators

Platform architecture

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.

  • Java 17
  • Spring Boot
  • Angular
  • Hibernate
  • SAML 2.0
  • Docker
  • from working documentation — to be approved

High-level architecture

One container, two external dependencies

The frontend and backend are delivered as a single artefact. The components communicate over HTTPS and a REST API.

01 · User

  • Browsera standard web browser
  • Identity providerKeycloak · SAML 2.0 sign-in

HTTPS · redirect to sign-in

02 · sara.next application container

  • Frontend — Angular SPAstatic files served by the backend
  • API layerREST endpoints: accepting requests, returning results.
  • Business logicRequests, approvals, reviews, rules and validations.
  • Data accessObject-relational mapping, connection pool, change history.
  • Integration layerCommunication with the identity provider and external systems.

03 · Data and integrations

  • Relational databaseSQL Server or PostgreSQL
  • Target systemsREST, Microsoft Graph, OData, SQL
  • SMTP servere-mail notifications

from the backend only

Illustrative diagram based on the architecture documentation.

Technology stack

Mature, widely known technologies

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.

The sara.next technology stack
AreaTechnologyRole
FrontendAngular (SPA), TypeScriptThe user interface; communicates only with the backend.
BackendJava 17, Spring BootREST API, business logic, integrations, serving the frontend.
DataRelational database, Hibernate / JPAApplication data, configuration, historical and audit data.
SecuritySpring Security, SAML 2.0Sign-in through the identity provider, authorisation on the application side.
IntegrationsREST, Microsoft Graph, OData, SQLData synchronisation and executing changes in target systems.
API documentationOpenAPIA description of the backend REST interfaces.
Getting startedDockerOne image: backend, frontend and the Java environment.

Data

A relational database as the single source of truth

01

What is stored

Users and permissions, access granting and review processes, configuration, historical and audit data.

02

Database engine

Connection via JDBC. Microsoft SQL Server and PostgreSQL are supported.

03

Change history

Data changes are versioned, which makes it possible to analyse the history of record modifications.

04

Diagram

Updated with migration scripts when a new version is deployed.

Integrations

Five operations per integration

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
Auto-implementation operations
OperationNameScope
createCreating accessAdding a user to a group, role, project, team or resource.
modifyModifying accessChanging the scope, level or parameters of existing access.
swapChange of userTransferring access to another person, e.g. when covering for someone.
removeRemoving accessRevoking a membership, role or assignment.
verifyExecution verificationChecking whether the state in the application matches the decision.

Talk to our technical team

We will discuss the architecture, requirements and integration model for the applications you want to start with.