|Manuals

Primary Brokers

The Primary Broker functions as the central operational component of Thinfinity® Workspace, responsible for serving the web interface that facilitates user ingress to the dashboard. It integrates with identity providers (IdPs), manages user session lifecycle, and directs users to appropriate resources based on their credentials and permissions. Additionally, it oversees the management and routing of virtualization workloads, ensuring optimal performance and resource allocation.

Key Roles and Responsibilities of the Primary Broker

Authentication and Authorization

The Primary Broker is central to user authentication and authorization, ensuring integration with external identity providers. It manages user authentication, validates user credentials against IdPs or through 2FA, and integrates with Microsoft Active Directory, OAuth, and SAML.

It also enforces access control, including policy-based access control and role-based permissions, to ensure users can only access authorized resources.

User Session Handling

It is responsible for managing user sessions, orchestrating session initiation, and coordinating session logistics. It handles user requests and directs them to appropriate application pools or resources.

Resource Allocation and Management

It allocates resources and manages resource distribution. Dynamically allocates resources based on real-time demand and availability.

It manages traffic and directs user requests to the appropriate application pools or VPCs. Optimizes the performance of virtual desktops and applications by managing the virtualization process.

Interaction with the Gateway

It operates in conjunction with the Gateway, which forwards authentication requests to the Primary Broker. The Primary Broker, in turn, participates in establishing secure reverse connections with the Gateway.

Interaction with the Secondary Brokers

The Primary Broker works alongside the Secondary Brokers (when they exist) for enhanced scaling and networking. It manages connection routing and load balancing for internal and external users, working with Secondary Brokers to allocate remote resources. The Primary Broker also monitors their activity and performs load balancing among them.

Security Features

The Primary Broker is integral to Thinfinity’s ZTNA architecture. It enforces the principle of least privilege access (PoLP), emphasizes continuous authentication by validating credentials and monitoring sessions, and embodies policy-based access control by coordinating the security policies. Does not require inbound port openings on internal networks and communicates with the Gateway via outbound WebSockets and TLS 1.3 encryption.

Deployment Location

Generally positioned within the target or internal network infrastructure. Alternatively, in certain configurations, it may reside within a DMZ or cloud environment. The component can be deployed on the same host as the Gateway to facilitate simplified deployment scenarios or on a dedicated host in distributed deployment architectures.

Note

While the Primary Broker and Gateway can reside on the same or separate hosts, they are delivered via a single unified installer.

  • Single-Host Setup: Choose All-in-one role after installation then use the Broker tab from the Configuration Manager to configure both components.
  • Distributed Setup: Install the package on separate machines, then use the Services tab in the Configuration Manager to select only the specific role (Gateway or Broker) required for that host.
Reference

For further information regarding configuration parameters, please refer to the Broker Tab page in the Reference chapter.

For comprehensive guidance on configuring production settings, see Thinfinity Workspace: Best Practices for Production Environments.