Open matthewreesstephenson opened 3 years ago
@matthewreesstephenson The username parameter is case-sensitive for the authentication endpoint used by these tools. Check that it matches exactly how it appears in AGOL. The normal OAuth view is case-insensitive so it's more flexible.
Have used this previously but now get an error message indicating "Unable to generate token. Invalid username or password. (error code: 400)". Using the same credentials I use for AGO. Not sure what the issue is. Only major difference is I have recently upgraded to pro 2.7.2.