apigee
Minor issue with default key/secret for Hello World App
Just I minor issue I ran into when running this.
In the last step when you use the identity facade with the Hello World App, if you create credentials for the App in the GUI the combined Key and Secret result in a Base64 encoded string that gets a space inserted into it because of length. This doesn't work when inserted in the header to authorize the client. As a work around, I had to use the api to create a different set of credentials with a shorter key and secret so when they are combined and base64 encoded they don't include a space. It would be easy enough to include this step in the instructions.
Hello @charterj , I guess the last step you mention is the POST request related to the token issuance.
I did the test with a client app (not the dummy app) and it works well in my case: I can authenticate the app on Apigee using a basic authorization header with the header value that is:
Basic base64(client_id+":"+client_secret)
But maybe I do not test the right part of the token delivery? In this case can you please tell me where the problem occurs and some more details on how you create the base64 value, plus any other details that can help to solve this issue.
