php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #69879 Unable to specify "realm"
Submitted: 2015-06-18 21:46 UTC Modified: -
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: public at aapconsulting dot com Assigned:
Status: Open Package: oauth (PECL)
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
24 + 44 = ?
Subscribe to this entry?

 
 [2015-06-18 21:46 UTC] public at aapconsulting dot com 
Description:
------------
I'm not sure if this is a bug report or a feature request.  According to what I've read in the OAuth 1.0 spec, the Authentication header "realm" is optional and therefore should be able to be included or not based on the specific case.  In my case, the provider is requiring this field and I have not been able to figure out how to include it.

Expected result:
----------------
My header should look something like this:

Authorization: OAuth realm="416100", 
oauth_consumer_key="XXXXXXXXXXXX",
oauth_signature_method="HMAC-SHA1",
oauth_nonce="XXXXXXXXXXXX",
oauth_timestamp="XXXXXXXXXXXX",
oauth_version="1.0",
oauth_token="XXXXXXXXXXXX",
oauth_signature="XXXXXXXXXXXX"


Actual result:
--------------
Authorization: OAuth oauth_consumer_key="XXXXXXXXXXXX",
oauth_signature_method="HMAC-SHA1",
oauth_nonce="XXXXXXXXXXXX",
oauth_timestamp="XXXXXXXXXXXX",
oauth_version="1.0",
oauth_token="XXXXXXXXXXXX",
oauth_signature="XXXXXXXXXXXX"

Patches

Pull Requests
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Thu Oct 30 15:00:01 2025 UTC