Identity Governance & Administration
sara.next
  1. sara.next
  2. Technology
  3. System requirements

Technology · Architecture

System requirements

To run sara.next you need a container environment, a relational database and an identity provider. Minimum values are listed below.

  • from working documentation — to be approved

Environment

Minimum requirements

Minimum requirements
ComponentRequirement
Container environmentDocker 20 or later, or a compatible container environment
CPUmin. 2 vCPU
RAMmin. 4 GB
Application port8080 (HTTP); HTTPS recommended in production
NetworkConnectivity to the database, the identity provider and integration services

Minimum values from the deployment documentation. The size of the production environment depends on the number of users and applications — to be determined during deployment.

Expert view

How to read the minimum requirements

The values below let you run the application and carry out a pilot. The size of the production environment depends on three factors: the number of users, the number of applications under control and — which often comes as a surprise — the review cycle.

A quarterly review generates short, intense load periods: within a few days thousands of reviewers sign in and make decisions, the system sends notifications and, at the end, generates removal requests. It is worth sizing the environment for these peaks, not for the average.

Database

The application works with Microsoft SQL Server and PostgreSQL. It is worth basing the choice on what the organisation already maintains: more important than the engine is whether the database is covered by backups, monitoring and recovery procedures.

Dependencies

External systems

External systems
SystemRoleNotes
Relational databaseApplication data, configuration, historyConnection via JDBC. Microsoft SQL Server and PostgreSQL are supported.
Identity providerUser sign-inKeycloak, SAML 2.0 protocol.
SMTP serverE-mail notificationsWith authentication and TLS.
Container registryImage distributionAny Docker-compatible registry.

Users

On the user side a browser is enough

Authentication and SSO

Access to the application

  • The application runs in a standard web browser
  • Sign-in through the organisation's identity provider — no separate password for sara.next
  • The user identifier is the e-mail address, which must be unique

See sara.next on your own scenarios

During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.