08-23-2022 05:01 PM
I am converting a REST Put snap so it can use OAuth2 for authentication purposes. I have a REST In-Memory OAuth2 account created. It has been able to authorize and refresh its tokens.
When I try and do a REST Put using this account, I am getting a 403 Forbidden error. I’m not sure what I’m doing wrong. The error_entity field in the the error view tells me that I have a missing equal sign in my authorization header. I’m not sure how I can fix this. Hoping someone might be able to tell me what I’m missing here.
I’ve included some screenshots of my OAuth2 account, my error messages, and the REST Put configuration. Suggestions would be greatly appreciated with my pre-emptive thanks.
Best…Alex
Solved! Go to Solution.
08-25-2022 09:28 AM
Resolved. I did everything correctly, with the exception of spelling my service URL right. Oooof.
08-25-2022 09:28 AM
Resolved. I did everything correctly, with the exception of spelling my service URL right. Oooof.