All services require a new token format
Scheduled Maintenance Report for Packet Broker
Completed
The scheduled maintenance has been completed.
Posted Dec 03, 2021 - 09:50 CET
In progress
We are currently updating Packet Broker infrastructure to require the OAuth 2.0 token audience.
Posted Dec 03, 2021 - 09:50 CET
Scheduled
All Packet Broker services will be requiring a new OAuth 2.0 token format presented by the client. The new token format includes an audience that needs to match the host name of the service.

Services using Packet Broker, including The Things Stack from version 3.15.2, will support this.

The Things Stack Cloud and The Things Stack Community Edition will be upgraded end of October according to schedule.

We advise customers using The Things Stack Enterprise and Open Source in combination with Packet Broker to upgrade to 3.15.2 shortly after its release.

This maintenance is not a security fix, but rather a preparation to use Packet Broker tokens more widely in third-party services. Including an audience in the security token allows services to verify that the token is intended for that service, and avoids third-party services to use the received token on other services. See https://datatracker.ietf.org/doc/html/rfc7519 for more information.
Posted Oct 02, 2021 - 21:00 CEST
This scheduled maintenance affected: Packet Broker Data Plane (Europe (eu), North America (nam), Asia-Pacific (apac)) and Packet Broker Global Services (Control Plane (cp.packetbroker.net), IAM (iam.packetbroker.net)).