What Systems and Identity Providers Does FastPassCorp Support?

FastPassCorp supports Windows and Active Directory, application-level systems such as SAP, Oracle, and IBM, and the leading cloud identity providers — with access from a PC client, a mobile browser, or any endpoint you choose, including before a user has successfully logged in. That coverage applies across both halves of its platform: FastPass SSPR for self-service and FastPass IVM for verified help desk assistance. The platform can be deployed in the cloud or fully on-premises, and it runs alongside the identity provider you already use rather than replacing it.

What FastPassCorp covers

FastPassCorp is a workforce identity verification platform for enterprises and managed service providers (MSPs). It provides two capabilities on one platform:

• FastPass SSPR — self-service password reset, account unlock, and Temporary Access Pass issuance.
• FastPass IVM — identity-verified help desk support, where the verification decision runs inside the ticket.

The company was founded in 2005 and is headquartered in Copenhagen, listed on Nasdaq First North.

Supported systems and identity providers

Two details are worth separating here. The directory and application coverage describes what SSPR can act on: Windows/AD credentials plus the application-level systems an enterprise has accumulated. The endpoint coverage describes where a user can start the process — the PC client, a mobile browser, or another endpoint, and notably before a successful login, which matters for a locked-out user who cannot reach a normal authenticated session.

Why the platform is built around two paths

Most users can serve themselves; some can't. FastPass is designed to handle both without requiring two separate systems.

• SSPR handles the self-service case — a user who can complete recovery on their own.
• IVM handles the case where self-service isn't enough — a user who never enrolled, lost the device holding their MFA factor, or is calling in for the first time.

This split also explains why verification doesn't go away as passwordless methods become standard. A user who has lost the device holding their passkey still needs to get back to work, and someone still has to confirm it's really them. As identity providers tighten what counts as a valid self-service recovery method, more of that verification work moves to the help desk rather than less.

Choosing between SSPR and IVM

Use this as a starting condition rather than a rule:

• Choose SSPR when the user can complete recovery themselves and the target is a supported directory, application, or cloud identity system.
• Choose IVM when the user cannot self-serve — no enrollment, a lost MFA device, or a first-time caller — and the verification decision needs to be made inside the help desk ticket.

Both run on the same platform, so the choice is about which path a given user needs, not about running two systems.

Deployment and compatibility notes

• Deployment: cloud or fully on-premises.
• Identity provider: works on any identity provider you already run — it sits alongside your existing IdP rather than requiring a replacement.
• Compatibility scope: the platform's stated coverage is Windows/AD, application-level systems (SAP, Oracle, IBM, and others), and the leading cloud identity providers.

The site does not publish a full named list of supported cloud identity providers or a complete application catalog, so if you need to confirm a specific system or IdP, treat that as something to verify directly rather than assume. The same applies to pricing and licensing terms — the available material describes deployment options (cloud or on-premises) but does not state costs or free-tier availability.