Solution · Identity and access

SAML single sign-on for every app, from one account.

Connect the applications your staff use over SAML 2.0. Each person signs in once, and their groups decide which apps they can open.

Applications in the AuthFI console.

Every application people sign in to

Web, mobile and machine clients, and the software that signs in over SAML. The page leads with what to fix first.

What changes

The problem as most companies have it today, and the same thing with AuthFI.

Today: A separate password for every application
With AuthFI: One sign-in, carried to every app over SAML
Today: Access is set app by app, by hand
With AuthFI: Apps are assigned to groups
Today: Setting up SAML means trading XML by email
With AuthFI: The metadata and certificate to hand over are on the app's page
Today: Leavers keep their app accounts
With AuthFI: Remove someone from a group and the app is gone for them

How it works

Each step, on the screen you would use.

Applications

Add an app, hand over its settings.

Register the application, then copy the sign-on address, entity id and certificate into it. That is the whole exchange.

SAML 2.0, and OpenID Connect for apps that prefer it

Metadata and certificate ready to copy

Assigned to groups

Applications in the AuthFI console.Applications in the AuthFI console.

People

Bring your existing directory.

People can keep signing in with the identity provider you already have, and AuthFI carries them on to every app.

Sign people in from Okta, Entra, Google and others

Passkeys and a second step on top

One record of every sign-in

Connections in the AuthFI console.Connections in the AuthFI console.

Put every app behind one sign-in.