Identity Governance & Administration
sara.next
  1. sara.next
  2. Technology
  3. Authentication and SSO

Technology · Security

Authentication and SSO

sara.next does not store passwords. Sign-in is delegated to the identity provider, and the application receives confirmation of identity via the SAML 2.0 protocol.

  • SAML 2.0
  • Service Provider
  • Keycloak as IdP
  • from working documentation — to be approved

Sequence diagram

SAML 2.0 sign-in

Browsersara.next (SP)Identity provider (IdP)01 Opening the application02 No active session03 Redirect to sign-in04 Authentication request05 User sign-in06 Signed SAML assertion07 Passing on the SAML response08 Signature verification, reading the e-mail09 User session

Expert view

Why an access management system should not have its own passwords

It would be ironic if an access control tool introduced yet another set of accounts and passwords to manage. sara.next delegates authentication to the organisation's identity provider. This brings three practical benefits.

  • The sign-in policy — password strength, multi-factor authentication, lockouts — is enforced in one place, in line with the organisation's standard.
  • Disabling an employee's account at the identity provider immediately cuts them off from sara.next as well.
  • A data leak from the application cannot reveal passwords, because there are none in it.

Authentication is not authorisation

It is worth separating these two concepts. The identity provider confirms who the user is. What they can do in the application — whether they see only their own access, the compliance panel or the configuration — is decided by sara.next itself, based on roles. These roles are managed just like any other access: through a request, approval and review.

Sign-in flow

Eight steps between the browser, the application and the IdP

  1. Entering the application

    The user opens sara.next in the browser.

  2. Session check

    The application checks whether an active session exists.

  3. Redirect to the IdP

    Without a session, the browser is sent to the identity provider's sign-in page.

  4. Authentication

    The user signs in using the method configured at the identity provider.

  5. SAML assertion

    The identity provider generates a signed confirmation of identity.

  6. Return to the application

    The browser passes the SAML response to sara.next.

  7. Verification

    The application checks the signature and validity of the response and reads the e-mail address.

  8. Session

    A local session is created; further access control is handled by the application.

Configuration

What needs to be agreed between the application and the IdP

Application address

The application identifier (Entity ID) on both sides.

IdP metadata

The SAML metadata address: certificates, sign-in and sign-out endpoints.

Application certificate

The key signing SAML messages, registered with the identity provider.

Post-logout address

Where the user goes after the session ends.

Users

Account synchronisation with the identity provider

Besides sign-in, the application can retrieve the list of users from the identity provider and keep a local copy of it for its processes.

How it works

  • A separate technical client with access to the identity provider's admin interface
  • Retrieving users, saving and updating data in the application database
  • The e-mail address as a shared identifier in both systems
  • The identity provider can be connected to the organisation's directory

Authorisation

After sign-in, the application decides

User roles

Access to functions depends on roles in sara.next.

Role permissions

The manager, compliance and administration panels are available only to authorised users.

Resource access rules

Control at the level of application requests and endpoints.

See sara.next on your own scenarios

During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.