This document outlines the setup and use of RTI Authentication for secure communication with third-party devices using client credentials.
Getting Started with RTI Authentication
Ensure software and firmware are updated: processor firmware must be 23.5.11 or higher, and Integration Designer must be 11.4 or higher.
Check for updates via Help – Check for Updates if automatic updates are not enabled.
Adding RTI Authentication to a System
Set up the project file with rooms, controllers, and drivers.
Configure driver properties and the system processor settings.
Confirm if drivers require authentication in the Authentication Dashboard; send the programming file to the processor if needed.
Upload the complete programming file and click Launch URL to verify drivers on the Authentication Dashboard.
Client Authentication Process
Send the RTI Authentication URL to the client for credential entry.
The client selects the device, clicks “Authorize,” enters credentials, and receives authorization approval.
Important Notes
Always update the Network Key when reusing program files, as a unique key is required for each system.
If a new network key is generated, a new URL link must be sent to the client.
The URL link does not expire unless a new network key is created.
Frequently Asked Questions
If a driver does not appear on the URL page, check driver version, configuration settings, and processor firmware.
Ensure client credentials match for RTI Authentication and the third-party site.
The authentication URL can be sent via text message and opened on various devices.
No user-interface commands are needed for the client; they can verify authorization by clicking the URL link.
📎 Attachments (1)
This article has 1 file attachment.