Overview
Overview of Fortified ID Access
Fortified ID Access is a modern Identity Provider (IdP) for organizations that need secure, flexible, standards-based access to applications, APIs, and digital services. This overview introduces Access, highlights its strengths, and shows how it fits the Swedish identity landscape.
Access combines authentication, authorization, identity enrichment, and federation support in one platform. For more about the product profile, see Why Access?. For practical examples, see Common use cases or More than Authentication.
Explore Access
Section titled “Explore Access”| Why Access? See where Access is especially strong and why organizations choose it. | why-access |
| Common Use Cases Connect Access capabilities to business needs and hands-on scenarios. | common-use-cases |
| Getting Started Follow the practical steps for configuring your first Access service. | getting-started |
| Key components Find authenticators, protocols, and the main Access building blocks. | key-components |
Why organizations choose Access
Section titled “Why organizations choose Access”Organizations choose Fortified ID Access when a basic login service is not enough—and when identity needs to work across real applications, users, and existing IT environments. Access brings secure authentication, SSO, MFA, passwordless options, federation, per-application login control, and identity enrichment together in one maintainable solution.
Make strong authentication fit the situation
Section titled “Make strong authentication fit the situation”Access lets organizations combine several authentication methods and choose which ones are available for a specific application, role, group, or user journey. Support for methods such as BankID, Freja eID, SITHS, certificates, OTP, and passkeys makes it possible to raise assurance where it matters without forcing every user through the same flow. Step-up authentication and multi-step flow control help apply stronger requirements exactly when an application or policy calls for them.
Connect applications without replacing the identity landscape
Section titled “Connect applications without replacing the identity landscape”Access can act as a SAML Identity Provider, an OIDC Provider, or a broker between applications and existing identity providers. Its protocol support covers modern and established environments, including SAML, OpenID Connect, ADFS, LDAP, JDBC, and REST-based integrations. This gives organizations a practical way to complement Entra ID, Google, ADFS, national federations, and existing directories while moving forward incrementally.
Turn identity data into useful access context
Section titled “Turn identity data into useful access context”Authentication is only part of the decision. Access can collect and transform information from directories, databases, HTTP services, Entra ID, and other sources, then use it in claims, assertions, tokens, and downstream application flows. Configurable modules and Pipes make it possible to normalize attributes, apply policy, select the right identity or role, and deliver the context each connected application needs—without creating a new custom integration for every variation.
Operate one platform across many environments
Section titled “Operate one platform across many environments”Access is built for organizations that need control over both security and operations. Configuration-driven modules, structured logging, audit and event support, and integration with Management Center make the platform easier to operate and monitor. It can run on Windows, Linux, or containers and fit on-premises, hybrid, and cloud deployments, so the same identity architecture can follow the organization as its environment evolves.
The result is an IdP platform that helps organizations improve security, simplify integration work, and give every connected application the right identity context. Access makes it possible to modernize authentication step by step, preserve investments in existing systems, and create a more consistent sign-in experience without turning each onboarding project into a custom development effort.
In this section