Skip to main content

Migration Guide: Updating Your Authentication Method

Until February 2025

As we roll out updates to improve our cloud platform, it's essential to migrate your authentication method to our new system. This guide will help you update to the reworked authentication layer, which includes enhanced security, better compatibility, and the introduction of OpenID Connect (OIDC) support. Please follow the steps below to ensure a smooth transition.

Affected Areas​

  • All API requests – both authorized and non-authorized.
  • All authentication requests – we have changed the service responsible for issuing access tokens.

Key Changes​

  • Deprecated Endpoints: The current authorization API endpoints (https://api.dronetag.app/v1/auth/*) are now deprecated. You must migrate to the new service (https://auth.dronetag.app).
  • OAuth 2.0 Credentials: Sign-in will now require OAuth 2.0 application credentials. Until automated OAuth 2.0 management is available, credentials will be issued manually.

Migration Timeline​

  • By the End of February 2025: Legacy authorization endpoints will be fully removed. All authorization requests must be migrated to the new service.

Step-by-Step Migration​

To simplify the transition, we recommend using an existing OIDC library for OAuth 2.0. These libraries manage the OAuth 2.0 flow, handling access tokens, refresh tokens, and other OIDC-related tasks.

You can find a list of certified OIDC implementations here: OpenID Connect Certified Libraries.

2. Migrate Authorization Requests to the New Auth Service​

All authorization requests must be migrated to the new endpoint:

  • Old Endpoint: POST https://api.dronetag.app/v1/auth/jwt/token
  • New Endpoint: POST https://auth.dronetag.app/realms/master/protocol/openid-connect/token

Ensure you update your request logic to point to the new URL and expect a different JSON response structure. The new response includes access_token and refresh_token fields, in addition to other fields.