Customers cannot provision
Incident Report for use.id
Postmortem

At December 16, 10:38 AM, we introduced new scopes in access tokens for applications and, in the same release, checked for the presence of these scopes in our endpoints. We noticed that several customers cached these tokens and hence, did not have the correct scopes. We have rolled back this release and will implement a fix where we first give out new tokens to make sure cached tokens contain the correct scopes.

Thank you for your patience and apologies for the inconvenience.

Posted Dec 16, 2022 - 11:08 CET

Resolved
This incident has been resolved.
Posted Dec 16, 2022 - 11:02 CET
Identified
The issue has been identified and a fix is being implemented.
Posted Dec 16, 2022 - 10:56 CET
Investigating
Some of our customers cannot provision accounts.
Posted Dec 16, 2022 - 10:38 CET
This incident affected: API.