You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is little documentation for the options available for tokenHost/tokenPath.
I was getting an error: "Access Token error The content-type is not JSON compatible" because I was entering the full path for a client_credentials token request.
It is required that the credentials.tokenPath be overridden or the default (and incorrect) path is used. This is not documented anywhere I could see. Had to parse the code to figure it out.
There is little documentation for the options available for tokenHost/tokenPath.
I was getting an error: "Access Token error The content-type is not JSON compatible" because I was entering the full path for a client_credentials token request.
It is required that the credentials.tokenPath be overridden or the default (and incorrect) path is used. This is not documented anywhere I could see. Had to parse the code to figure it out.
Hope this helps any other poor souls pulling their hair trying to figure it out. Perhaps the examples in the documentation could show this?
Here is a snippet of the index which show other defaults...
Pull request sent.
The text was updated successfully, but these errors were encountered: