Recently the login payload was changed from the lame-ass OAuth2 access token response format to non-underscored property names (as part of generally extending the returned properties to include certain user data).
This broke the ability to log in via Swagger, because that actually expects on OAuth2 format.
Task:
Reconfigure Swagger to look for the token via a different property name (if possible), or
Create a separate token response for Swagger (it already uses a separate controller action), or
Just change the name of the property back.
This bug doesn't affect "production", since Swagger is disabled in prod mode.
Recently the login payload was changed from the lame-ass OAuth2 access token response format to non-underscored property names (as part of generally extending the returned properties to include certain user data).
This broke the ability to log in via Swagger, because that actually expects on OAuth2 format.
Task:
This bug doesn't affect "production", since Swagger is disabled in prod mode.