Shared Instances: Federated Connections Between Reitti Servers

The Shared Instances feature enables cross-instance user connectivity and true federated sharing between different Reitti servers. This powerful capability allows you to connect with users on other Reitti instances, creating a distributed network of location data sharing while maintaining privacy and control.

Overview

Shared Instances replaces the legacy “Connected Accounts” feature with a more robust and flexible federation system. Instead of being limited to users on the same server, you can now:

• Connect with users on remote Reitti instances
• Share location data across different servers
• Maintain separate user management while enabling collaboration
• Audit API token usage for enhanced security

Key Features

Cross-Instance Connectivity

Connect with users on other Reitti instances via a straightforward UI under Settings > Integrations > Shared Instances`. This enables true federated sharing across different Reitti deployments.

Simple Setup Process

Establishing connections is straightforward:

1. Enter the remote instance’s URL
2. Provide the target user’s API token
3. Test and verify the connection
4. Start sharing location data

Setting Up Shared Instances

Prerequisites

• Reitti v1.3.0 or later on both instances
• Network connectivity between the instances
• Valid API tokens from the remote users

Configuration Steps

1. Navigate to Settings

   • Go to Settings > Integrations > Shared Instances

2. Add a New Shared Instance

   • Click “Add Shared Instance”
   • Enter the remote instance URL (e.g., https://reitti.example.com)
   • Provide the target user’s API token

3. Test the Connection

   • Use the built-in test functionality to verify the configuration
   • Ensure the remote instance is accessible and the API token is valid

4. Verify and Save

   • Complete the verification workflow
   • Save the configuration to establish the connection

User Interface

Shared Instances Overview

The new Shared Instances integration overview

Remote User Information

Detailed information modal for remote users

Security Considerations

API Token Management

• API tokens provide access to location data
• Regularly review and rotate tokens as needed
• Monitor token usage through the auditing interface
• Revoke tokens immediately if compromised

Network Security

• Use HTTPS for all instance connections
• Ensure proper firewall configuration
• Consider VPN connections for sensitive deployments
• Validate SSL certificates for remote instances

Data Privacy

• Shared data is subject to the privacy policies of both instances
• Users maintain control over what data is shared
• Connection can be terminated at any time
• Data sharing is bidirectional by default

Troubleshooting

Common Issues

Connection Failed

• Verify the remote instance URL is correct and accessible
• Check that the API token is valid and not expired
• Ensure network connectivity between instances
• Confirm the remote instance is running v1.3.0 or later

Authentication Errors

• Regenerate the API token on the remote instance
• Verify the token has appropriate permissions
• Check for any special characters in the token

Data Not Syncing

• Confirm both instances are online and accessible
• Check the API token usage logs for errors
• Verify the remote user has location data to share
• Review network connectivity and firewall settings

Support and Debugging

For additional support:

• Check the Reitti GitHub repository for known issues
• Review server logs for detailed error messages
• Use the connection test feature to diagnose problems
• Join the community discussions for help from other users

Best Practices

For Administrators

• Regularly audit API token usage
• Implement proper backup strategies for federated data
• Monitor network traffic and performance
• Keep instances updated to the latest version

For Users

• Regularly review connected instances
• Understand the data sharing implications