Passing Body Content in Post Snap
Hi,
This is a very novice question, but I am having trouble with a post request snap. This is just to authenticate with the RingCentral platform to receive a token for API consumption. I am able to...
Forum Discussion
We went ahead and tried it, since it is a sandbox account and it worked, but where do we go from here?
I think I missed something. Why move the credentials to pipeline parameters when you can just use account.username and account.password?
I’m wondering the same thing. I also wonder if maybe I just need to delete that account and recreate it?
Are you saying that you got it working by removing the account from the snap and replacing account.username and account.password with pipeline parameters in your HTTP Entity expression?
If that’s the case, it means the server is rejecting the request because of the Authorization header added by the account. So that does leave you in a tough spot, since the only way to keep the password secure is by using an account.
Let’s test that theory: Add an Authorization header to the version that works, to see if it breaks.
The Authorization header added by the Basic Auth account would have a value like
Basic bXl1c2VyOm15cCZzc3cwcmQ=
Yes that is what happened. There is a missing piece that you don’t know about yet. Basically there is already an Authorization header that is required by RingCentral. Basically you have to take an app id and client secret concatenate the two the base64 encode the concatenated string and pass that as your Authorization header. Didn’t mean to leave that out earlier. Just didn’t realize it would be relevant until now.
