Tivian Access Architectural Overview

Overview

This article provides an architectural overview of TIVIAN Access, a central authentication service powered by Okta.com and integrated into the TIVIAN platform. It includes diagrams illustrating the components involved in the architecture and common federation scenarios supported by the solution.

Information

This article focuses on the architectural aspects of TIVIAN Access, explaining its role in the overall platform and its integration with various authentication workflows.

• TIVIAN Access Introduction
• Architectural Components
• Federation Scenarios

TIVIAN Access Introduction

TIVIAN Access is powered by Okta.com and has been integrated into the overall TIVIAN platform to serve as a central service for all authentication workflows. It acts as the Identity provider for the platform, ensuring secure and efficient user authentication across various components.

Architectural Components

The architecture of TIVIAN Access involves several components working together to provide a comprehensive authentication solution. The following diagram illustrates these components and their relationships:

Federation Scenarios

TIVIAN Access supports various federation scenarios, allowing for flexible and secure authentication across different systems and services. The following illustration demonstrates some common federation scenarios supported by the solution:

 

FAQ

What is TIVIAN Access?

TIVIAN Access is the product name for the Identity provider in the TIVIAN platform. It is powered by Okta.com and serves as a central service for all authentication workflows within the platform.

Why is Okta.com used for TIVIAN Access?

Okta.com is a leading provider of identity and access management solutions. By leveraging Okta's technology, TIVIAN Access can offer robust, secure, and scalable authentication services for the platform.

What are federation scenarios?

Federation scenarios refer to different ways in which TIVIAN Access can integrate with and authenticate users across various systems, applications, or organizations. These scenarios demonstrate the flexibility of the solution in handling diverse authentication requirements.