Resolved -
We experienced a limited scope issue with authorization following a deployment early this morning. In rare cases, when the uid was passed as an integer--not a string--authorization would fail to validate the uid.
While we do recommend always passing the uid as a string--and state as such in our documentation--edge cases where the uid was an integer weren't covered in tests.
We've since pushed a fix, will include these edge cases in the future, and no changes are required on your side at this time.
May 12, 11:58 PDT
Identified -
We're currently experiencing some issues with authentication. This seems to be low impact, and most customers will not be affected. We've identified the issue, however, and are currently working on deploying a fix.
May 12, 11:23 PDT