Use these Credentials to access your RSTAR Affinity tenant. IMSURGE uses them to load Site and Instrument choices during setup and to authenticate data requests during pipeline execution. If the correct Credentials already exist in your workspace, select them instead of creating another set.

Setup

Prerequisites

You need the HTTPS address of your Affinity tenant, an API Client ID, and its API Client Secret.

An Organization Admin can create API user credentials in the Affinity dashboard under User Management → Add API User. Use credentials with access to the sites and instruments you want to import.

Create the Credentials

When setting up the RSTAR Affinity source in IMSURGE, choose New Credentials and enter a descriptive name and the following fields:

Field Description Required
Server Hostname Your tenant’s HTTPS base URL, for example https://example.rstaraffinity.cloud. Omit /api, embedded credentials, query parameters, and fragments. ✓
API Client ID The client ID of your Affinity API user. ✓
API Client Secret The client secret associated with that client ID. ✓

Save the Credentials, then select them in the RSTAR Affinity source setup. IMSURGE obtains OAuth access tokens automatically; you do not enter an access token yourself.

Site, Instrument, and Sensor Index belong to the integration, not to these Credentials. Choose Site and Instrument from the queried dropdowns, then enter Sensor Index explicitly. There is no default sensor index.

Reuse and Credential Changes

You can reuse these Credentials across integrations that access the same Affinity tenant. If you rotate the client credentials in Affinity, update the saved Credentials in IMSURGE; associated integrations use the new values.

API Client ID and API Client Secret are encrypted at rest and hidden when editing saved Credentials. The Client Secret input is masked. Leave credential fields blank on edit to keep their existing values.

Troubleshooting

  • Invalid Server Hostname — Enter the HTTPS base URL only. Remove any /api path or query string.
  • Authentication or permission error during setup — Confirm the tenant address and API credentials, and check that the API user can access the expected sites and instruments. Saving Credentials validates the fields locally; API access is checked when loading setup choices.
  • Empty Site or Instrument list — Confirm the API user has access to the intended tenant and site. Instrument choices depend on the selected Site.
  • HTTP 429 — Avoid repeated setup refreshes and reduce execution frequency if requests are rate-limited. IMSURGE recommends Every Hour for scheduled polling; live tenant rate limits remain unverified.

The integration is an offline-tested alpha. Live authentication and retrieval remain unverified. An instrument appearing in a dropdown does not guarantee that its output is supported. See the source guide’s alpha limitations before testing.