[GH-ISSUE #233] OAuth signature different with the one RESTClient(Firefox plugin) generated #130

New issue

Closed

opened 2026-03-03 16:45:56 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 16:45:56 +03:00

Owner

Originally created by @likers on GitHub (May 27, 2016).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/233

Hello, I found it's quite weird that the signatures generated using OAuthSwift and using RESTClient are different, the parameters are totally the same.
Thus the server returned error: "401 oauth_problem=signature_invalid" when I use the OAuthSwift's signature, on the other hand RESTClient's signature get passed.
Do I need to do anything on server side or I have to modify the signature algorithm if needed?
Thank you.

Originally created by @likers on GitHub (May 27, 2016). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/233 Hello, I found it's quite weird that the signatures generated using OAuthSwift and using RESTClient are different, the parameters are totally the same. Thus the server returned error: "401 oauth_problem=signature_invalid" when I use the OAuthSwift's signature, on the other hand RESTClient's signature get passed. Do I need to do anything on server side or I have to modify the signature algorithm if needed? Thank you.