FAQ

IDombud eID is a digital service identification solution where organizations can issue, manage and revoke identities for employees, consultants and other people on assignment. The solution is designed for organizations that need high trust, clear lifecycle management and better control over how the identity is used.

A private eID is linked to the individual as a private person. IDombud eID is instead linked to the individual's role or function in the organization. This makes it more suitable for work-related sign-in, access to internal systems and situations where identity needs to be governed by organizational rules.

Yes. IDombud eID can be used with existing identity and authorization infrastructure, such as directories, federation solutions and other sign-in flows. This makes it possible to introduce service identification without replacing the full current environment.

Yes. IDombud eID can be delivered both as a service and for self-hosted operation. This allows organizations to choose the model that best fits their requirements for control, security, operations and responsibility.

IDombud eID is particularly suitable for organizations with high requirements for secure identity governance, such as the public sector, healthcare, critical operations and other regulated environments. It is also relevant for organizations that need to manage identities for more than employees, such as partners, consultants or external contractors.

IAM is about identifying users and giving them the right access to systems and services. IGA focuses more on governance, lifecycle, approvals, reviews and traceability so that access remains correct over time.

IdP stands for Identity Provider. It is the service that authenticates the user and sends a secure assertion to the application about who the user is, often including attributes or access context.

LoA stands for Level of Assurance and describes the trust level of an identity or sign-in. A higher level usually means stronger controls for issuance, authentication and identity management.

Fortified ID helps municipalities create a cohesive identity architecture for employees, consultants, students, guardians and citizens. The focus is secure authentication, correct authorization and solutions that work with both modern and legacy systems.

Yes. The solutions can be adapted by user group, risk level and use case. An organization can combine BankID, Freja eID, SITHS, EFOS, passkeys, certificates and internal directories within the same architecture.

Yes. Fortified ID builds solutions that can integrate with national eIDs and federation models while the organization keeps control of attributes, rules and access.

Fortified ID develops and delivers solutions for digital identity, strong authentication, access governance, federation, integration and digital trust. We often work in environments where security, user experience and compliance need to work together.

Yes. Many implementations start with a clear use case, such as MFA, BankID, SSO, delegated administration or access to a specific application. The solution can then be expanded with more methods, integrations and user groups.

Yes. Fortified ID works with both modern cloud services and existing on-premises environments. Common integration patterns include SAML, OpenID Connect, SCIM, APIs, directories, certificates and federations.