Skip to content

OpenSky integration broken for registered accounts due to new OAuth2 authentication requirement #932

Description

@geekasylum

Hi! The OpenSky Network recently updated their authentication rules and permanently retired legacy HTTP Basic Authentication (passing raw usernames and passwords in the request header) across their endpoints. They now require clients to use an OAuth2 token exchange flow to authenticate.

Because the integration is still attempting to use the old username/password method, OpenSky's servers are silently dropping the credentials. This forces all users straight into the anonymous guest tier, which is strictly limited to 400 requests per day.
For anyone tracking a local zone, this 400-request limit runs out in just a few hours. Once exhausted, the integration hits a 429 Too Many Requests error and all entities go completely unavailable.

Expected Behavior

Registered OpenSky users should be able to log in to unlock their standard 4,000 daily requests (and 8,000 for data contributors/feeders) so the integration can run continuously without hitting the anonymous rate-limiting wall.

Suggested Fix

The integration needs a small update to handle the new OpenSky OAuth2 token handshake, where it can swap the account client credentials for a Bearer token and append Authorization: Bearer to the standard data queries.

Thanks for your hard work maintaining this integration!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions