UPDATE (Resolution): The issue should now be addressed across the board. The preliminary fix (in order to allow for a quicker fix) did not depend on changing the Authorization Extension code so if you look at the linked PR you may still see it open for a while. There will likely be changes in the extension in order to better support the requirement that originally triggered the error, but any future changes will now have in consideration the root cause of the issue so any changes will be transparent to you. If you still experience the issue let me know (or if you can confirm that it’s already resolved then it would even be better).
Sorry for the radio silence; this question was quickly followed by an answer that diminished the visibility of the question (a completely unanswered question will sit on the unanswered queue which gives it greater visibility).
If you’re reading this, in the future please avoid providing answers that are not in fact solutions to the problem and just contain additional information or state that you’re also experiencing the same issue; please use comments for that!
If you’re the original author of the question you can proactively ask those answers to be moved to comments.
Moving to what’s important; the fact there is indeed an issue. As @maxime.ribera already noted we are aware of the issue and there is already a PR with a fix. However, the updated code still needs to be deployed and reach you so we are also considering if there’s quicker alternatives to address this. As additional information you can also now keep track of updates to this situation through the following incident.