|November 2022 DSB ReST API Component Change||Milestones||Status||Notification|
|Final Documentation Available||17 October 2022||Ongoing|
|UAT Release||6 August 2022||Completed||2022-07-18 Notification|
|Final Go/No-Go Decision (November)||2 November 2022||Completed||Release postponed.|
|Final Go/No-Go Decision (March)||15 March 2023||Ongoing|
|Production and UAT2 Release||19 March 2023||Ongoing|
|DSB ID||Title||Type||Github||Change Request|
|DSB-1806||Basic Authentication Bug||Component Upgrade||N/A||N/A|
- Users that do not already adhere to RFC-7617 will not be able to send REST API requests if they do not update their authentication method.
- Therefore, Users who do not already adhere to RFC-7617 must update their Authentication header. You may refer to section 2.1 of the REST RoE for the authentication changes. The latest REST RoE can be found here.
- The DSB’s UAT environment will be unavailable between 12:00 AM UTC on the Saturday of the UAT Release weekend and 12:00 PM UTC on the Sunday of the UAT Release weekend to allow for the implementation.