Tivian Access

Increase the security of your TIVIAN applications

English | Deutsch

To increase the security of your TIVIAN applications - after the implementation of the Privacy Assistant (GDPR) - the new TIVIAN Access module has been implemented. By the use of this module, that can be integrated into your existing SSO infrastructure, bad password habits will be mitigated.

Three Main Scenarios

Multi Factor Authentication

Partner Setup

You want to add an extra layer of security to my EFS login by using a second authentication factor.

You want to access all my EFS installations & modules that I manage for my clients using one set of login credentials.

Federated Login

You want all users to access EFS (admin, portals, report manager) by using our existing corporate sign in that we are using for all 3rd party products. The integration with an existing SSO software or service is based on the supported protocols OIDC Federation or SAML Federation.

→ Read more about OIDC Federation

→ Read more about SAML Federation

Please note that scenario C can be configured with or without a connection to an existing identity provider. A second authentication factor can be enforced here as well.

Identity Providers and Protocols

Read more about the pre-requisites for a successful connection to an existing IAM/SSO via SAML 2.0 or OpenID connect.

→ Read more

Architectural Overview

Read more about the various components that have been integrated into the TIVIAN Access architecture.

→ Read more

FAQ

An Identity Provider is a service which is used to handle authentication for other services. The authentication process is specified by protocols.
It is commonly used to achieve Single-Sign-On (SSO) across multiple applications.

A few common ones are:

https://www.okta.com/
https://auth0.com/
Social Identity Providers (Facebook, Twitter, Google)

We integrate with customer’s Identity Providers using standardised protocols. An architectural overview can be found here: https://qbdocs.atlassian.net/wiki/spaces/QA/pages/1559232524

Also Okta offers documentation on integration with external Identity Providers

For a more detailed description please have a look at OpenID Connect or SAML 2.0 on how they do authentication for apps. This applies because our Identity Provider is an application from the customer’s perspective.

We support Identity Providers which support authentication via the protocol SAML 2.0 or OpenID Connect. They also have to be publicly available (not in a private network).
It does not matter if it is a cloud hosted service or an on-premise solution. Due to the fact that every piece of software implements a protocol slightly different, each Identity Provider has to be tested so that we can guarantee that it works.

These are the providers which have been tested and where the setup is known.

Please have a look at the list of familiar Identity Providers

Not familiar does not mean not working. Please contact support or the IAM team to find out if an integration is possible or not.