|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #61691 OAuthProvider does not get encoded
Submitted: 2012-04-10 18:05 UTC Modified: 2012-08-24 09:01 UTC
Avg. Score:4.5 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:1 (50.0%)
From: niels dot van dot hecke at gmail dot com Assigned:
Status: Open Package: oauth (PECL)
PHP Version: 5.3.10 OS: Ubuntu 10.04.4 LTS
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: niels dot van dot hecke at gmail dot com
New email:
PHP Version: OS:


 [2012-04-10 18:05 UTC] niels dot van dot hecke at gmail dot com
When running a simple oauth consumer-provider script, signature mismatches occure because the sent signature (generated by the OAuth class) is encoded according to specifications but the calculated signature (generated by the OAuthProvider class) is not. Checking the two signatures causes errors and the authentication fails.
EG. consumer generates:3qBMmue4Q%2Bj8Dm4%2F9VSTl6y0TR8%3D
provider generates: 3qBMmue4Q+j8Dm4/9VSTl6y0TR8=

From manual page:


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-08-21 17:57 UTC] hans at shapeways dot com
This seems related to what I'm seeing at
 [2012-08-24 09:01 UTC] niels dot van dot hecke at gmail dot com
Not really, because the consumer generated and provider generated strings are identical, just that the provider does not escape the string. I 'fixed' this by ULR encoding the string on the provider side and manually checking signatures.
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Fri Aug 14 17:01:26 2020 UTC