HTTP 403 - "User to be acted on does not match subject in bearer token"

Using the Management API with an M2M Application.

client gets HTTP 403 responses for user read requests.

The following Error occurs: "com.auth0.exception.APIException: Request failed with status code 403: User to be acted on does not match subject in bearer token."
 

Steps to reproduce

1. Create M2M application and new API
2. Add scopes with "current_user" scopes to the API
3. User the management API using an access_token with this API

• HTTP 403 error
• current_user scope
• M2M application

Having "current_user" scopes in a M2M app conflicts and returns the error.

The workaround solution is to:

• Omit  `current_user` scopes when requesting the tokens for the M2M app.