Working with pre-signed requests with oAuth Echo #120

Open
tarnfeld opened this Issue Jul 2, 2011 · 6 comments

Projects

None yet

2 participants

tarnfeld commented Jul 2, 2011

Hey,

I've been using EpiTwitter for a while now and am very reluctant to find another class since this one is so awesome! I was wondering if anybody knew how I could inject these seven attributes into the EpiTwitter workflow to generate a signed request to twitter? This is for an implementation oAuth Echo.

  • oauth_consumer_key
  • oauth_token
  • oauth_signature_method
  • oauth_signature
  • oauth_timestamp
  • oauth_nonce
  • oauth_version

Thanks!
Tom.

tarnfeld commented Jul 2, 2011

Scrap that! I've written two methods, does anyone think it's working forking and making a pull request for this?

You would use this method if you were going to be a Consumer in the oAuth Echo workflow, eg: connecting to TwitPic:
EpiTwitter::echoHeaders();

If you were going to be the Delegator in the oAuth Echo workflow, you would get the sent header and push it into this:
EpiTwitter::echoVerifyCredentials($x_verify_credentials_authorization_header);

Thoughts?

Owner
jmathai commented Jul 5, 2011

@tarnfeld - definitely fork and issue a pull request. If you could add a unit test that'd be great but not mandatory (I can do that).

Owner
jmathai commented Jul 15, 2011

Tom, I've been really swamped and wanted to st least let you know this is on
my lust of things to look at but I don't have an eta. -- Jaisen

On Jul 2, 2011 12:50 AM, "tarnfeld" <
reply@reply.github.com>
wrote:

Hey,

I've been using EpiTwitter for a while now and am very reluctant to find
another class since this one is so awesome! I was wondering if anybody knew
how I could inject these seven attributes into the EpiTwitter workflow to
generate a signed request to twitter? This is for an implementation oAuth
Echo
.

  • oauth_consumer_key
  • oauth_token
  • oauth_signature_method
  • oauth_signature
  • oauth_timestamp
  • oauth_nonce
  • oauth_version

Thanks!
Tom.

Reply to this email directly or view it on GitHub:
#120

That's ok, I've already implemented it but probably needs refinement and could work better. Have an "echoHeaders" and "echo" method. The first generates an array of the headers you send to post to a oAuth Echo API and the latter is to make the twitter request with those headers.

Sent from my iPhone

On 15 Jul 2011, at 08:29, jmathaireply@reply.github.com wrote:

Tom, I've been really swamped and wanted to st least let you know this is on
my lust of things to look at but I don't have an eta. -- Jaisen

On Jul 2, 2011 12:50 AM, "tarnfeld" <
reply@reply.github.com>
wrote:

Hey,

I've been using EpiTwitter for a while now and am very reluctant to find
another class since this one is so awesome! I was wondering if anybody knew
how I could inject these seven attributes into the EpiTwitter workflow to
generate a signed request to twitter? This is for an implementation oAuth
Echo
.

  • oauth_consumer_key
  • oauth_token
  • oauth_signature_method
  • oauth_signature
  • oauth_timestamp
  • oauth_nonce
  • oauth_version

Thanks!
Tom.

Reply to this email directly or view it on GitHub:
#120

Reply to this email directly or view it on GitHub:
#120 (comment)

Owner
jmathai commented Jul 15, 2011

If you added this to twitter-async then could you send a pull request?

On Jul 14, 2011 11:49 PM, "tarnfeld" <
reply@reply.github.com>
wrote:

That's ok, I've already implemented it but probably needs refinement and
could work better. Have an "echoHeaders" and "echo" method. The first
generates an array of the headers you send to post to a oAuth Echo API and
the latter is to make the twitter request with those headers.

Sent from my iPhone

On 15 Jul 2011, at 08:29, jmathaireply@reply.github.com wrote:

Tom, I've been really swamped and wanted to st least let you know this is
on
my lust of things to look at but I don't have an eta. -- Jaisen

On Jul 2, 2011 12:50 AM, "tarnfeld" <
reply@reply.github.com>
wrote:

Hey,

I've been using EpiTwitter for a while now and am very reluctant to find
another class since this one is so awesome! I was wondering if anybody
knew
how I could inject these seven attributes into the EpiTwitter workflow to
generate a signed request to twitter? This is for an implementation
oAuth
Echo
.

  • oauth_consumer_key
  • oauth_token
  • oauth_signature_method
  • oauth_signature
  • oauth_timestamp
  • oauth_nonce
  • oauth_version

Thanks!
Tom.

Reply to this email directly or view it on GitHub:
#120

Reply to this email directly or view it on GitHub:
#120 (comment)

Reply to this email directly or view it on GitHub:
#120 (comment)

Yeah I will do, just needs tidying up and am on holiday at the mo. It's tested pretty well and currently running in production.

Sent from my iPhone

On 15 Jul 2011, at 08:51, jmathaireply@reply.github.com wrote:

If you added this to twitter-async then could you send a pull request?

On Jul 14, 2011 11:49 PM, "tarnfeld" <
reply@reply.github.com>
wrote:

That's ok, I've already implemented it but probably needs refinement and
could work better. Have an "echoHeaders" and "echo" method. The first
generates an array of the headers you send to post to a oAuth Echo API and
the latter is to make the twitter request with those headers.

Sent from my iPhone

On 15 Jul 2011, at 08:29, jmathaireply@reply.github.com wrote:

Tom, I've been really swamped and wanted to st least let you know this is
on
my lust of things to look at but I don't have an eta. -- Jaisen

On Jul 2, 2011 12:50 AM, "tarnfeld" <
reply@reply.github.com>
wrote:

Hey,

I've been using EpiTwitter for a while now and am very reluctant to find
another class since this one is so awesome! I was wondering if anybody
knew
how I could inject these seven attributes into the EpiTwitter workflow to
generate a signed request to twitter? This is for an implementation
oAuth
Echo
.

  • oauth_consumer_key
  • oauth_token
  • oauth_signature_method
  • oauth_signature
  • oauth_timestamp
  • oauth_nonce
  • oauth_version

Thanks!
Tom.

Reply to this email directly or view it on GitHub:
#120

Reply to this email directly or view it on GitHub:
#120 (comment)

Reply to this email directly or view it on GitHub:
#120 (comment)

Reply to this email directly or view it on GitHub:
#120 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment