> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/access/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/access/readme.md).

# 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?](/access/readme/why-access.md). For practical examples, see [Common use cases](/access/common-use-cases.md) or [More than Authentication](/access/readme/more-than-authentication.md).

## Explore Access

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Why Access?</strong><br>See where Access is especially strong and why organizations choose it.</td><td><a href="/access/readme/why-access.md">Why Access?</a></td></tr><tr><td><strong>Common Use Cases</strong><br>Connect Access capabilities to business needs and hands-on scenarios.</td><td><a href="/access/common-use-cases.md">Common Use Cases</a></td></tr><tr><td><strong>Getting Started</strong><br>Follow the practical steps for configuring your first Access service.</td><td><a href="/access/getting-started.md">Getting Started</a></td></tr><tr><td><strong>Key components</strong><br>Find authenticators, protocols, and the main Access building blocks.</td><td><a href="/access/key-components.md">Key components</a></td></tr></tbody></table>

## 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

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

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

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

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fortifiedid.se/access/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.