Tags Architecture

Architecture

Architecture Capabilities

Functional capabilities are described in the functional description of the solutions. Runtime capabilities The runtime capabilities describe the architecture capabilities the different solutions provide during runtime operations. An example could be authorization. The architecture provides the capability to authorize access to resources. Since Altinn 3 is a platform letting its users develop applications and deploy them, you will see that many capabilities that typical is DevOps capabilities in other projects, is part of the runtime capabilities. »

Runtime arhictecture capabilities

The Runtime (exceution) Architecture supports applications at run-time. It is a unified collection of run-time technology services, capabilities, control structures, and supporting infrastructure upon which application software runs. The below capability map shows the different runtime capabilities grouped by different areas. Runtime capability map Download as Visio Application build & deploy capabiltiesApplication developers using Altinn Studio to create Applications have access to build & deploy capabilties Application development capabilitiesApplication development capabilities are capabilites that is used for developing applications in Altinn Studio »

Application Components

For a functional overview of the different solutions part see solutions Application Construction ComponentsApplication Construction Components refers to the required components and configurations needed to create the different applications in the different solutions. Non-Solution-SpecificNon-Solution-Specific Application components refer to all components other than the core solution or solution-specific Application typical used for devops. »

Development & Operations Capabilities

It covers the full spectrum of capabilities, starting with development, going through a transition to operations, and ending with operations. Each capability comprises people, procedures, and software and hardware tools. This documentation currently focuses on the capabilities that others can learn from and reuse. See below for a capability map and the different DevOps capability areas. Full screen Analysis & Design CapabilitiesAnalysis & Design Capabilities are the capabilities needed to analyze needs and design solutions and applications for the Altinn 3 platform. »

Fremdriftsplaner for modernisering av Altinn Autorisasjon

Innen juni 2025 så skal dagens Altinn løsning være modernisert og migrert til skyen. Det innebærer at mye av dagens løsning må utvikles på nytt. Overordnet målsetning for modernisering Autorisasjon skal være en selvstendig komponent og eget produkt Sikre en robust og sikker drift samtidig som vi understøtter stor vekst i bruken av autorisasjon. Øke endringstakten i Autorisasjon slik at veien fra behov til løsning blir raskere. Forbedre og forenkle brukerflyten slik at det blir enklere å administrere tilganger Tilby nye og moderne API som gjør det enklere å integrere mot og ta i bruk Altinn Autorisasjon som tilgangsstyringløsning for andre offentlige tjenester Hva skal gjøres? »

XACML - Altinn Studio

The standard defines a declarative fine-grained, attribute-based access control policy language, an architecture, and a processing model describing how to evaluate access requests according to the rules defined in policies. The Altinn Studio and Altinn Studio Apps solution uses the XACML standard for the following XACML Reference Architecture: Used as input for defining the Altinn Studio Apps authorization architecture XACML Policy: Used to define the authorization rules for apps XACML Request: Format used for PEP to call PDP XACML Response: Format used for response from PDP to PEP. »

Application construction components - Altinn Events

System architecture illustration When a publish request is posted to the /app endpoint, the event will first be saved in the events-registration queue for operational resilience and flexibility. When an event retrieval request is received, it will respond with results from the internal relational database used for events persistence. Altinn Event Architecture Flow for processing a single incoming event Sequence diagram - POST event System and service dependencies Internal Altinn Authorization: used to authorize access to endpoints Altinn Register: used to support lookup on alternative subject External Azure Kubernetes Services: hosts the docker containers for microservices and cron jobs in a fully managed Kubernetes cluster PostgreSQL: used for storage Azure Functions: used internally to process and forward incoming cloud events to subscriber webhooks. »

Application construction components - Altinn Notifications

System architecture illustration The solution is supported by multiple cron jobs running in the same Kubernetes cluster, a Kafka server and an instance of Azure Communication services. The following diagram illustrates the overall data flow. Solution diagram Altinn Notifications Process flow between microservices and Kafka topics Vis/skjul innhold Flow chart for order processing Flow chart including Kafka topics for order processing Vis/skjul innhold Flow chart for email notification processing Flow chart including Kafka topics for email notification processing Vis/skjul innhold Flow chart for sms notification processing Flow chart including Kafka topics for sms notification processing System and service dependencies Internal Altinn Authorization: used to authorize access to endpoints Altinn Profile: used to retrieve recipient information Altinn Register: used to retrieve recipient information The number of internal dependencies for Notifications is currently quite limited, but during 2024 we expect the services below to be utilized by Notifications. »

Kafka

Kafka topic overview Below is an overview of the Kafka topics used in our system, along with information about the producers and the content of each topic Health Vis/skjul innhold altinn.notifications.health.check Description: A topic dedicated to verifying the connectivity between microservices and the Kafka cluster. Event trigger: External party has requested that the health of the microservice is checked. Producer: Altinn Notifications, KafkaHealthCheck Content: Format: string Description: A string not intended to carry any significant data. »

Altinn 3 Broker Transition Solution

About Altinn 3 Broker Transition SolutionWhat is the Altinn 3 Broker Transition Solution Getting started with Altinn Broker Transition SolutionHow to get started using the Broker Transition solution from Altinn 2 to Altinn 3 Technical OverviewThe Altinn 3 Broker Transition Solution allows service owners who own broker services in Altinn 2 to point those services towards Altinn 3 using an internal Altinn 2 bridge. UsageHow to use the Altinn 3 Broker Transition solution. »