/auth/AuthorizeSensor: Authorize a client device on behalf of a logged-in tenant user/API-Key.

POST 
/auth/AuthorizeSensor

What
Enables a tenant-authorized backend to directly authorize a client (sensor) after the user has authenticated in the browser.

How the flow works

1. The sensor opens an authorization URL in the browser.
2. If the user is logged in, authorization continues immediately; otherwise, they are prompted to log in.
3. After successful login at the tenant system, the tenant backend calls this endpoint.
4. The client device is then authorized and receives a signed and authorized configuration.

Who
Tenant admins (and higher).

Login
Login or API key (both allowed).

Request

Responses

200

OK

404

Client or tenant not found.
Usually the tenant will always exist in this flow — if you see this error, the missing client is the most likely cause.

500

Internal login failure.
This typically indicates an unexpected internal error unrelated to user input.