- Check if your non-SSO password is correct set
- Double check if your internal application is active
- Verify whether private key is correct
- It might that application is not correctly created – i.e., it is not created as Internal application
- Try to generate token by your self using the following curl script:
curl --request POST -H 'Content-Type: application/x-www-form-urlencoded' -H "Content-Type: application/json" -d grant_type=password -d username='admin_username' -d password='admin_password' -d client_id='your_client_key' -d client_secret='your_client_secret_key' -d scope='Egnyte.filesystem Egnyte.permission Egnyte.audit Egnyte.link Egnyte.user Egnyte.group' https://your_domain.egnyte.com/puboauth/token
What the error messages mean
- The Egnyte API client key is not created as an Internal Application. Your Egnyte application is configured only for the Implicit Grant flow, and cloudHQ cannot use that type. Create a new application and select Internal Application (for own company use only) as the application type.
- The Egnyte API client key is not valid. Check your keys in the Egnyte Developer console.
- The Egnyte API secret key is not valid. Check the secret key of your application in the same Developer console.
- The provided Egnyte username and password are not correct. If you use SSO, check your non-SSO username and password. To verify them, log in to Egnyte and click My Profile, then My Preferences.
- Unable to generate Egnyte OAuth token. cloudHQ also shows the error reported by Egnyte. Go through the checks above and try to generate the token yourself with the curl script.