I too wonder if this is an actual bug. Is it documented somewhere that the concept of the 'unscoped_token' from v2 has been cancelled?
I too wonder if this is an actual bug. Is it documented somewhere that the concept of the 'unscoped_token' from v2 has been cancelled?