[twitter-dev] Re: Twitter OAuth Problem
Actually I was able to turn the switch on and also make these changes.
Neither fixed the problem. Still getting the 401 error. I know OAuth
has been down today but it is working at least for now.
On Jul 20, 2:57 pm, Elmseeker wrote:
> in twitteroauth.php you will find 4 lines
>
> function accessTokenURL() { return 'https://api.twitter.com/oauth/
> access_token'; }
> function authenticateURL() { return 'https://twitter.com/oauth/
> authenticate'; }
> function authorizeURL() { return 'https://twitter.com/oauth/
> authorize'; }
> function requestTokenURL() { return 'https://api.twitter.com/oauth/
> request_token'; }
>
> the 2 in the middle need to be changed to:
>
> function authenticateURL() { return 'https://api.twitter.com/oauth/
> authenticate'; }
> function authorizeURL() { return 'https://api.twitter.com/oauth/
> authorize'; }
>
> hope this helps.
>
> On Jul 20, 11:02 am, Gabe wrote:
>
>
>
> > Hi,
>
> > I have been using Abraham's OAuth library and I *almost* have it
> > working. I'm a longtime C++ developer but new to Twitter API. Anyway,
> > it took me a while to use the callback.php file as the actual call
> > back. That (I thought) was the missing element, I was under the
> > impression that the "test.php" file in his library could be
> > substituted for the callback. Anyway when I realized the mistake I
> > was happy to implement the new code. The new callback is being called
> > but I am consistently getting HTTP Error Code 401 (unauthorized) when
> > it is being used, and I am using it basically "as is". Any insight
> > would be appreciated.
>
> > Note - I did regenerate my application registration recently - how
> > long does it take for those credentials to be usable?
>
> > Thanks much.
>
> > -Gabe
Re: [twitter-dev] Re: Twitter OAuth Problem
We've got a somewhat confusing setup right now in this area, admittedly.
For most purposes, the twitter.com app registration area should be thought
of as deprecated. Though that area doesn't display the correct paths for
OAuth operations, assume that you should be using the api subdomain.
As for the setting for "Sign in with Twitter" -- we managed to not provide
that toggle on the dev.twitter.com app registration setup -- you can
re-enable it on the (deprecated) twitter.com app area.
Way less than optimal, but it's the way it is at the moment.
Issues with saving/creating apps should be just about resolved now as well.
Taylor
On Tue, Jul 20, 2010 at 12:22 PM, Gabe wrote:
> I did notice something odd about that. My app page on Twitter says the
> opposite tho - to remove the "api.". I will try your suggestion and
> thanks!!
>
> On Jul 20, 2:57 pm, Elmseeker wrote:
> > in twitteroauth.php you will find 4 lines
> >
> > function accessTokenURL() { return 'https://api.twitter.com/oauth/
> > access_token'; }
> > function authenticateURL() { return 'https://twitter.com/oauth/
> > authenticate'; }
> > function authorizeURL(){ return 'https://twitter.com/oauth/
> > authorize'; }
> > function requestTokenURL() { return 'https://api.twitter.com/oauth/
> > request_token'; }
> >
> > the 2 in the middle need to be changed to:
> >
> > function authenticateURL() { return 'https://api.twitter.com/oauth/
> > authenticate'; }
> > function authorizeURL(){ return 'https://api.twitter.com/oauth/
> > authorize'; }
> >
> > hope this helps.
> >
> > On Jul 20, 11:02 am, Gabe wrote:
> >
> >
> >
> > > Hi,
> >
> > > I have been using Abraham's OAuth library and I *almost* have it
> > > working. I'm a longtime C++ developer but new to Twitter API. Anyway,
> > > it took me a while to use the callback.php file as the actual call
> > > back. That (I thought) was the missing element, I was under the
> > > impression that the "test.php" file in his library could be
> > > substituted for the callback. Anyway when I realized the mistake I
> > > was happy to implement the new code. The new callback is being called
> > > but I am consistently getting HTTP Error Code 401 (unauthorized) when
> > > it is being used, and I am using it basically "as is". Any insight
> > > would be appreciated.
> >
> > > Note - I did regenerate my application registration recently - how
> > > long does it take for those credentials to be usable?
> >
> > > Thanks much.
> >
> > > -Gabe
>
[twitter-dev] Re: Twitter OAuth Problem
I did notice something odd about that. My app page on Twitter says the
opposite tho - to remove the "api.". I will try your suggestion and
thanks!!
On Jul 20, 2:57 pm, Elmseeker wrote:
> in twitteroauth.php you will find 4 lines
>
> function accessTokenURL() { return 'https://api.twitter.com/oauth/
> access_token'; }
> function authenticateURL() { return 'https://twitter.com/oauth/
> authenticate'; }
> function authorizeURL() { return 'https://twitter.com/oauth/
> authorize'; }
> function requestTokenURL() { return 'https://api.twitter.com/oauth/
> request_token'; }
>
> the 2 in the middle need to be changed to:
>
> function authenticateURL() { return 'https://api.twitter.com/oauth/
> authenticate'; }
> function authorizeURL() { return 'https://api.twitter.com/oauth/
> authorize'; }
>
> hope this helps.
>
> On Jul 20, 11:02 am, Gabe wrote:
>
>
>
> > Hi,
>
> > I have been using Abraham's OAuth library and I *almost* have it
> > working. I'm a longtime C++ developer but new to Twitter API. Anyway,
> > it took me a while to use the callback.php file as the actual call
> > back. That (I thought) was the missing element, I was under the
> > impression that the "test.php" file in his library could be
> > substituted for the callback. Anyway when I realized the mistake I
> > was happy to implement the new code. The new callback is being called
> > but I am consistently getting HTTP Error Code 401 (unauthorized) when
> > it is being used, and I am using it basically "as is". Any insight
> > would be appreciated.
>
> > Note - I did regenerate my application registration recently - how
> > long does it take for those credentials to be usable?
>
> > Thanks much.
>
> > -Gabe
[twitter-dev] Re: Twitter OAuth Problem
in twitteroauth.php you will find 4 lines
function accessTokenURL() { return 'https://api.twitter.com/oauth/
access_token'; }
function authenticateURL() { return 'https://twitter.com/oauth/
authenticate'; }
function authorizeURL(){ return 'https://twitter.com/oauth/
authorize'; }
function requestTokenURL() { return 'https://api.twitter.com/oauth/
request_token'; }
the 2 in the middle need to be changed to:
function authenticateURL() { return 'https://api.twitter.com/oauth/
authenticate'; }
function authorizeURL(){ return 'https://api.twitter.com/oauth/
authorize'; }
hope this helps.
On Jul 20, 11:02 am, Gabe wrote:
> Hi,
>
> I have been using Abraham's OAuth library and I *almost* have it
> working. I'm a longtime C++ developer but new to Twitter API. Anyway,
> it took me a while to use the callback.php file as the actual call
> back. That (I thought) was the missing element, I was under the
> impression that the "test.php" file in his library could be
> substituted for the callback. Anyway when I realized the mistake I
> was happy to implement the new code. The new callback is being called
> but I am consistently getting HTTP Error Code 401 (unauthorized) when
> it is being used, and I am using it basically "as is". Any insight
> would be appreciated.
>
> Note - I did regenerate my application registration recently - how
> long does it take for those credentials to be usable?
>
> Thanks much.
>
> -Gabe
[twitter-dev] Re: Twitter OAuth Problem
I think I might have answered my own question. It seems when I created the new app registration I forgot to check the box at the bottom which says to use Twitter for login. Now Twitter won't let me change it. I expect that will fix it. On Jul 20, 2:02 pm, Gabe wrote: > Hi, > > I have been using Abraham's OAuth library and I *almost* have it > working. I'm a longtime C++ developer but new to Twitter API. Anyway, > it took me a while to use the callback.php file as the actual call > back. That (I thought) was the missing element, I was under the > impression that the "test.php" file in his library could be > substituted for the callback. Anyway when I realized the mistake I > was happy to implement the new code. The new callback is being called > but I am consistently getting HTTP Error Code 401 (unauthorized) when > it is being used, and I am using it basically "as is". Any insight > would be appreciated. > > Note - I did regenerate my application registration recently - how > long does it take for those credentials to be usable? > > Thanks much. > > -Gabe
