Federation¶

The Federation page configures TAK server federation — the ability to share CoT data between multiple TAK servers. Federation allows MAGK to connect with other TAK servers (including government TAK Server instances) for cross-organization situational awareness.

Federation Overview¶

Federation creates a peer-to-peer connection between TAK servers. When federated, servers share CoT data (position reports, markers, chat messages) according to configured sharing rules.

graph LR
    A[MAGK Server] <-->|Federated Connection| B[Remote TAK Server]
    A <-->|Federated Connection| C[Another TAK Server]

Each federated connection is independent — you can federate with multiple servers simultaneously with different sharing rules for each.

Federate List¶

The federate list displays all configured federation connections.

Column	Description
Name	Federate display name
Address	Remote server address and port
Status	Connected, Disconnected, or Error
Direction	Outgoing, Incoming, or Bidirectional
Last Connected	Timestamp of the last successful connection
Data Shared	Summary of shared data types

Creating a Federate Connection¶

Click Add Federate to configure a new federation connection.

Form Fields¶

Field	Type	Required	Description
Name	Text	Yes	Display name for this federate
Address	Text	Yes	Remote TAK server address (hostname or IP)
Port	Number	Yes	Remote server federation port (typically 9000 or 9001)
Protocol	Select	Yes	TCP or SSL
Direction	Select	Yes	Outgoing, Incoming, or Bidirectional
Certificate	File	Conditional	Remote server's CA certificate (required for SSL connections)
Auto-Connect	Toggle	No	Automatically connect when the TAK service starts

SSL Federation¶

For SSL-based federation (recommended), both servers must trust each other's CA certificates:

Export your MAGK TAK CA certificate from the Certificates page
Provide it to the remote server administrator
Import the remote server's CA certificate when creating the federate connection

Certificate Trust

Both servers must import each other's CA certificates for SSL federation to work. Coordinate with the remote server administrator before attempting to connect.

Configure what data is shared with each federate from the federate detail view under the Sharing tab.

Data Type	Description
Position Reports	Player and asset position CoT messages
Chat Messages	Text chat messages between users
Markers	User-placed map markers and points of interest
Sensor Data	AIS, ADS-B, and other sensor-to-CoT data
Missions	Mission and objective data

Each data type can be independently enabled or disabled per federate connection.

Group Filtering¶

Optionally restrict federation data sharing to specific groups:

Setting	Description
Share All Groups	All CoT data is shared regardless of group membership
Selected Groups	Only CoT data from selected groups is shared with this federate
Exclude Groups	Share all data except from excluded groups

Connection Management¶

Connecting¶

Click Connect on a federate entry to establish the connection. The status indicator updates to show connection state:

Status	Description
🟢 Connected	Active federation connection, data is flowing
🔴 Disconnected	No active connection
🟡 Connecting	Connection attempt in progress
⚠️ Error	Connection failed — check the error message for details

Disconnecting¶

Click Disconnect to gracefully close the federation connection. The remote server is notified of the disconnection.

Connection Logs¶

View federation connection logs from the federate detail view under the Logs tab. Logs include connection attempts, data transfer summaries, and error messages.

Certificates — CA certificates for SSL federation
Data Packages — Federated server data packages
Teams — Team-based data sharing filters (uses TAK server groups internally)
Settings — TAK service federation port configuration