Cloud Agent teknisk dokument

  1. The cloud agent connects to OSR’s data gateway and starts listening for requests. It is ensured that it is OSR’s server by verification of the certificate for the domain.
  2. A user runs a report, triggering a request from OSR’s reporting server to the data gateway.
  3. The data gateway finds the established connection with the customer’s agent and passes on the request. The actual process of finding the corresponding agent is done using a Pairing Key that is a manually transferred secret that is entered into the OSR Portal by the customer administrator.
  4. The agent looks up the credentials and settings for the requested data source and executes the request; be it a query against an SQL server or reading a file.
  5. The agent reads the result data from the data source.
  6. The agent starts streaming back the result data to the data gateway.
  7. The data gateway passes on the stream to the reporting service.

Note that all report queries are run directly on the ERP system; thus, always providing up-to-date information. The data generated by queries and retrieved files are not stored by OSR in the cloud in any other form than rendered reports. The agent creates an outbound connection to OSR’s servers. It communicates on outbound port TCP 443. The agent does not require any inbound ports. If you are experiencing connectivity issues due to firewall constraints it is recommended that you whitelist the IP addresses for the Azure North Europe region in your firewall. You can download the Microsoft Azure Datacenter IP list, which is updated weekly. The agent communicates with the servers via HTTPS using the fully qualified domain name (FQDN). The current domain name is gateway.onestopreporting.com.

Merk

Traffic going to visualstudio.com or visualstudioonline.com are for app telemetry and insights and are not required for the agent to function.

Sist endret 02.10.2025