> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote: > It will work for reader/atom/* . It doesn't however work for > subscriptions/export . If this is a problem I can see about getting it > added.
It will be great if it would work for subscriptions/export, I think many clients use OPML export.
>> To unsubscribe from this group, send email to fougrapi+ >> unsubscribegooglegroups.com or reply to this email with the words "REMOVE >> ME" as the subject.
> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
It uses SignPost for OAuth. It's generic java code run from desktop, but can be used for Android with some modifications.
I am yet to test all calls to make sure they work with OAuth, but this is a good start.
Brad, could you enable OAuth on subscriptions/export request? My android app (ReaderScope) uses it to download OPML data.
Also, one question to Google Reader team. Is the OAuth support an experiment or can I start using it in real world and deploy it in my app? (I know GReader API is not official, but I just want to make sure that OAuth won't go away all of a sudden)
On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
> -- > Jayesh
> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote:
>> It will work for reader/atom/* . It doesn't however work for >> subscriptions/export . If this is a problem I can see about getting it >> added.
> It will be great if it would work for subscriptions/export, I think many > clients use OPML export.
> I will try to test the new OAuth later today.
> Thanks for quick reply.
>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>> -- >>> Jayesh
>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>> Hello friends,
>>>> It was asked in a previous thread if we could provide OAuth capabilities >>>> for accessing Reader data. We recently enabled OAuth support for Reader. You >>>> can find relevant information here: >>>> http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>> Awesome. If this works, it will be the best solution to get user logged >>> in w/o username/password.
>>> To unsubscribe from this group, send email to fougrapi+ >>> unsubscribegooglegroups.com or reply to this email with the words >>> "REMOVE ME" as the subject.
>> To unsubscribe from this group, send email to fougrapi+ >> unsubscribegooglegroups.com or reply to this email with the words "REMOVE >> ME" as the subject.
I have enabled OAuth on the subscription export so you should be able to use that as well now.
I can't say definitively what Google is going to do with respect to auth systems, however OAuth is not experimental, I fully expect its support to outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that users don't have to provide Google credentials to third party applications.
On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > Ok, I got the OAuth working with Google Reader (at least for subscription > list).
> It uses SignPost for OAuth. It's generic java code run from desktop, but > can be used for Android with some modifications.
> I am yet to test all calls to make sure they work with OAuth, but this is a > good start.
> Brad, could you enable OAuth on subscriptions/export request? My android > app (ReaderScope) uses it to download OPML data.
> Also, one question to Google Reader team. Is the OAuth support an > experiment or can I start using it in real world and deploy it in my app? (I > know GReader API is not official, but I just want to make sure that OAuth > won't go away all of a sudden)
> Thanks again for the OAuth support. > -- > Jayesh
> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>> -- >> Jayesh
>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>> It will work for reader/atom/* . It doesn't however work for >>> subscriptions/export . If this is a problem I can see about getting it >>> added.
>> It will be great if it would work for subscriptions/export, I think many >> clients use OPML export.
>> I will try to test the new OAuth later today.
>> Thanks for quick reply.
>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>>> -- >>>> Jayesh
>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com>wrote:
>>>>> Hello friends,
>>>>> It was asked in a previous thread if we could provide OAuth >>>>> capabilities for accessing Reader data. We recently enabled OAuth support >>>>> for Reader. You can find relevant information here: >>>>> http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>>> Awesome. If this works, it will be the best solution to get user logged >>>> in w/o username/password.
>>>> To unsubscribe from this group, send email to fougrapi+ >>>> unsubscribegooglegroups.com or reply to this email with the words >>>> "REMOVE ME" as the subject.
>>> To unsubscribe from this group, send email to fougrapi+ >>> unsubscribegooglegroups.com or reply to this email with the words >>> "REMOVE ME" as the subject.
> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> wrote: > I have enabled OAuth on the subscription export so you should be able to > use that as well now.
> I can't say definitively what Google is going to do with respect to auth > systems, however OAuth is not experimental, I fully expect its support to > outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that > users don't have to provide Google credentials to third party applications.
> -Brad
> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>> Ok, I got the OAuth working with Google Reader (at least for subscription >> list).
>> It uses SignPost for OAuth. It's generic java code run from desktop, but >> can be used for Android with some modifications.
>> I am yet to test all calls to make sure they work with OAuth, but this is >> a good start.
>> Brad, could you enable OAuth on subscriptions/export request? My android >> app (ReaderScope) uses it to download OPML data.
>> Also, one question to Google Reader team. Is the OAuth support an >> experiment or can I start using it in real world and deploy it in my app? (I >> know GReader API is not official, but I just want to make sure that OAuth >> won't go away all of a sudden)
>> Thanks again for the OAuth support. >> -- >> Jayesh
>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>> -- >>> Jayesh
>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>> It will work for reader/atom/* . It doesn't however work for >>>> subscriptions/export . If this is a problem I can see about getting it >>>> added.
>>> It will be great if it would work for subscriptions/export, I think many >>> clients use OPML export.
>>> I will try to test the new OAuth later today.
>>> Thanks for quick reply.
>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>>>> -- >>>>> Jayesh
>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com>wrote:
>>>>>> Hello friends,
>>>>>> It was asked in a previous thread if we could provide OAuth >>>>>> capabilities for accessing Reader data. We recently enabled OAuth support >>>>>> for Reader. You can find relevant information here: >>>>>> http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>>>> Awesome. If this works, it will be the best solution to get user logged >>>>> in w/o username/password.
>>>>> To unsubscribe from this group, send email to fougrapi+ >>>>> unsubscribegooglegroups.com or reply to this email with the words >>>>> "REMOVE ME" as the subject.
>>>> To unsubscribe from this group, send email to fougrapi+ >>>> unsubscribegooglegroups.com or reply to this email with the words >>>> "REMOVE ME" as the subject.
>> To unsubscribe from this group, send email to fougrapi+ >> unsubscribegooglegroups.com or reply to this email with the words "REMOVE >> ME" as the subject.
> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> wrote:
>> I have enabled OAuth on the subscription export so you should be able to >> use that as well now.
>> I can't say definitively what Google is going to do with respect to auth >> systems, however OAuth is not experimental, I fully expect its support to >> outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that >> users don't have to provide Google credentials to third party applications.
>> -Brad
>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>> Ok, I got the OAuth working with Google Reader (at least for subscription >>> list).
>>> It uses SignPost for OAuth. It's generic java code run from desktop, but >>> can be used for Android with some modifications.
>>> I am yet to test all calls to make sure they work with OAuth, but this is >>> a good start.
>>> Brad, could you enable OAuth on subscriptions/export request? My android >>> app (ReaderScope) uses it to download OPML data.
>>> Also, one question to Google Reader team. Is the OAuth support an >>> experiment or can I start using it in real world and deploy it in my app? (I >>> know GReader API is not official, but I just want to make sure that OAuth >>> won't go away all of a sudden)
>>> Thanks again for the OAuth support. >>> -- >>> Jayesh
>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>>> -- >>>> Jayesh
>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com>wrote:
>>>>> It will work for reader/atom/* . It doesn't however work for >>>>> subscriptions/export . If this is a problem I can see about getting it >>>>> added.
>>>> It will be great if it would work for subscriptions/export, I think many >>>> clients use OPML export.
>>>> I will try to test the new OAuth later today.
>>>> Thanks for quick reply.
>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com>wrote:
>>>>>> -- >>>>>> Jayesh
>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com>wrote:
>>>>>>> Hello friends,
>>>>>>> It was asked in a previous thread if we could provide OAuth >>>>>>> capabilities for accessing Reader data. We recently enabled OAuth support >>>>>>> for Reader. You can find relevant information here: >>>>>>> http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>>>>> Awesome. If this works, it will be the best solution to get user >>>>>> logged in w/o username/password.
>>>>>> To unsubscribe from this group, send email to fougrapi+ >>>>>> unsubscribegooglegroups.com or reply to this email with the words >>>>>> "REMOVE ME" as the subject.
>>>>> To unsubscribe from this group, send email to fougrapi+ >>>>> unsubscribegooglegroups.com or reply to this email with the words >>>>> "REMOVE ME" as the subject.
>>> To unsubscribe from this group, send email to fougrapi+ >>> unsubscribegooglegroups.com or reply to this email with the words >>> "REMOVE ME" as the subject.
>> To unsubscribe from this group, send email to fougrapi+ >> unsubscribegooglegroups.com or reply to this email with the words "REMOVE >> ME" as the subject.
>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>> I have enabled OAuth on the subscription export so you should be able to use that as well now. >>> I can't say definitively what Google is going to do with respect to auth systems, however OAuth is not experimental, I fully expect its support to outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that users don't have to provide Google credentials to third party applications. >>> -Brad >>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>> Ok, I got the OAuth working with Google Reader (at least for subscription list). >>>> Here is example code: >>>> http://pastebin.com/VbusAELq >>>> It uses SignPost for OAuth. It's generic java code run from desktop, but can be used for Android with some modifications. >>>> I am yet to test all calls to make sure they work with OAuth, but this is a good start. >>>> Brad, could you enable OAuth on subscriptions/export request? My android app (ReaderScope) uses it to download OPML data. >>>> Also, one question to Google Reader team. Is the OAuth support an experiment or can I start using it in real world and deploy it in my app? (I know GReader API is not official, but I just want to make sure that OAuth won't go away all of a sudden) >>>> Thanks again for the OAuth support. >>>> -- >>>> Jayesh
>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>> -- >>>>> Jayesh
>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>>> It will work for reader/atom/* . It doesn't however work for subscriptions/export . If this is a problem I can see about getting it added.
>>>>> It will be great if it would work for subscriptions/export, I think many clients use OPML export. >>>>> I will try to test the new OAuth later today. >>>>> Thanks for quick reply.
>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>>>> -- >>>>>>> Jayesh
>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>>>>> Hello friends, >>>>>>>> It was asked in a previous thread if we could provide OAuth capabilities for accessing Reader data. We recently enabled OAuth support for Reader. You can find relevant information here: http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>>>>>> Awesome. If this works, it will be the best solution to get user logged in w/o username/password.
>>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > Hi Brad, > Now I am stuck on edit-tags, it is returning 401 Unauthorized with OAuth.
>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>> I have enabled OAuth on the subscription export so you should be able to use that as well now. >>>> I can't say definitively what Google is going to do with respect to auth systems, however OAuth is not experimental, I fully expect its support to outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that users don't have to provide Google credentials to third party applications. >>>> -Brad >>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>> Ok, I got the OAuth working with Google Reader (at least for subscription list). >>>>> Here is example code: >>>>> http://pastebin.com/VbusAELq >>>>> It uses SignPost for OAuth. It's generic java code run from desktop, but can be used for Android with some modifications. >>>>> I am yet to test all calls to make sure they work with OAuth, but this is a good start. >>>>> Brad, could you enable OAuth on subscriptions/export request? My android app (ReaderScope) uses it to download OPML data. >>>>> Also, one question to Google Reader team. Is the OAuth support an experiment or can I start using it in real world and deploy it in my app? (I know GReader API is not official, but I just want to make sure that OAuth won't go away all of a sudden) >>>>> Thanks again for the OAuth support. >>>>> -- >>>>> Jayesh
>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>>> -- >>>>>> Jayesh
>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>>>> It will work for reader/atom/* . It doesn't however work for subscriptions/export . If this is a problem I can see about getting it added.
>>>>>> It will be great if it would work for subscriptions/export, I think many clients use OPML export. >>>>>> I will try to test the new OAuth later today. >>>>>> Thanks for quick reply.
>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>>>>> -- >>>>>>>> Jayesh
>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>>>>>> Hello friends, >>>>>>>>> It was asked in a previous thread if we could provide OAuth capabilities for accessing Reader data. We recently enabled OAuth support for Reader. You can find relevant information here: http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>>>>>>> Awesome. If this works, it will be the best solution to get user logged in w/o username/password.
>>>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
> Please let me know if you find something wrong about these end points > on google reader side. > -- > Jayesh
> On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: >> Hi Brad, >> Now I am stuck on edit-tags, it is returning 401 Unauthorized with OAuth.
>>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>> I have enabled OAuth on the subscription export so you should be able to use that as well now. >>>>> I can't say definitively what Google is going to do with respect to auth systems, however OAuth is not experimental, I fully expect its support to outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that users don't have to provide Google credentials to third party applications. >>>>> -Brad >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>>> Ok, I got the OAuth working with Google Reader (at least for subscription list). >>>>>> Here is example code: >>>>>> http://pastebin.com/VbusAELq >>>>>> It uses SignPost for OAuth. It's generic java code run from desktop, but can be used for Android with some modifications. >>>>>> I am yet to test all calls to make sure they work with OAuth, but this is a good start. >>>>>> Brad, could you enable OAuth on subscriptions/export request? My android app (ReaderScope) uses it to download OPML data. >>>>>> Also, one question to Google Reader team. Is the OAuth support an experiment or can I start using it in real world and deploy it in my app? (I know GReader API is not official, but I just want to make sure that OAuth won't go away all of a sudden) >>>>>> Thanks again for the OAuth support. >>>>>> -- >>>>>> Jayesh
>>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>>>> -- >>>>>>> Jayesh
>>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>>>>> It will work for reader/atom/* . It doesn't however work for subscriptions/export . If this is a problem I can see about getting it added.
>>>>>>> It will be great if it would work for subscriptions/export, I think many clients use OPML export. >>>>>>> I will try to test the new OAuth later today. >>>>>>> Thanks for quick reply.
>>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>>>>>>> -- >>>>>>>>> Jayesh
>>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com> wrote:
>>>>>>>>>> Hello friends, >>>>>>>>>> It was asked in a previous thread if we could provide OAuth capabilities for accessing Reader data. We recently enabled OAuth support for Reader. You can find relevant information here: http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>>>>>>>>> Awesome. If this works, it will be the best solution to get user logged in w/o username/password.
>>>>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>>>>> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
> > Please let me know if you find something wrong about these end points > > on google reader side. > > -- > > Jayesh
> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi <jayeshsa...@gmail.com> > wrote: > >> Hi Brad, > >> Now I am stuck on edit-tags, it is returning 401 Unauthorized with > OAuth.
> >>>> Let me know. > >>>> Thanks > >>>> -- > >>>> Jayesh
> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> > wrote:
> >>>>> I have enabled OAuth on the subscription export so you should be able > to use that as well now. > >>>>> I can't say definitively what Google is going to do with respect to > auth systems, however OAuth is not experimental, I fully expect its support > to outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that > users don't have to provide Google credentials to third party applications. > >>>>> -Brad > >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi <jayeshsa...@gmail.com> > wrote:
> >>>>>> Ok, I got the OAuth working with Google Reader (at least for > subscription list). > >>>>>> Here is example code: > >>>>>> http://pastebin.com/VbusAELq > >>>>>> It uses SignPost for OAuth. It's generic java code run from desktop, > but can be used for Android with some modifications. > >>>>>> I am yet to test all calls to make sure they work with OAuth, but > this is a good start. > >>>>>> Brad, could you enable OAuth on subscriptions/export request? My > android app (ReaderScope) uses it to download OPML data. > >>>>>> Also, one question to Google Reader team. Is the OAuth support an > experiment or can I start using it in real world and deploy it in my app? (I > know GReader API is not official, but I just want to make sure that OAuth > won't go away all of a sudden) > >>>>>> Thanks again for the OAuth support. > >>>>>> -- > >>>>>> Jayesh
> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi < > jayeshsa...@gmail.com> wrote:
> >>>>>>> -- > >>>>>>> Jayesh
> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> > wrote:
> >>>>>>>> It will work for reader/atom/* . It doesn't however work for > subscriptions/export . If this is a problem I can see about getting it > added.
> >>>>>>> It will be great if it would work for subscriptions/export, I think > many clients use OPML export. > >>>>>>> I will try to test the new OAuth later today. > >>>>>>> Thanks for quick reply.
> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi < > jayeshsa...@gmail.com> wrote:
> >>>>>>>>> -- > >>>>>>>>> Jayesh
> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes <bhaw...@google.com> > wrote:
> >>>>>>>>>> Hello friends, > >>>>>>>>>> It was asked in a previous thread if we could provide OAuth > capabilities for accessing Reader data. We recently enabled OAuth support > for Reader. You can find relevant information here: > http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
> >>>>>>>>> Awesome. If this works, it will be the best solution to get user > logged in w/o username/password.
> >>>>>>>>> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
> >>>>>>>> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
> >>>>>> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
> >>>>> To unsubscribe from this group, send email to fougrapi+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
>> > Please let me know if you find something wrong about these end points >> > on google reader side. >> > -- >> > Jayesh
>> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi <jayeshsa...@gmail.com> >> > wrote: >> >> Hi Brad, >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized with >> >> OAuth.
>> >>>> Let me know. >> >>>> Thanks >> >>>> -- >> >>>> Jayesh
>> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> >> >>>> wrote:
>> >>>>> I have enabled OAuth on the subscription export so you should be >> >>>>> able to use that as well now. >> >>>>> I can't say definitively what Google is going to do with respect to >> >>>>> auth systems, however OAuth is not experimental, I fully expect its support >> >>>>> to outlast ClientLogin. We actually prefer OAuth to ClientLogin now so that >> >>>>> users don't have to provide Google credentials to third party applications. >> >>>>> -Brad >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi >> >>>>> <jayeshsa...@gmail.com> wrote:
>> >>>>>> Ok, I got the OAuth working with Google Reader (at least for >> >>>>>> subscription list). >> >>>>>> Here is example code: >> >>>>>> http://pastebin.com/VbusAELq >> >>>>>> It uses SignPost for OAuth. It's generic java code run from >> >>>>>> desktop, but can be used for Android with some modifications. >> >>>>>> I am yet to test all calls to make sure they work with OAuth, but >> >>>>>> this is a good start. >> >>>>>> Brad, could you enable OAuth on subscriptions/export request? My >> >>>>>> android app (ReaderScope) uses it to download OPML data. >> >>>>>> Also, one question to Google Reader team. Is the OAuth support an >> >>>>>> experiment or can I start using it in real world and deploy it in my app? (I >> >>>>>> know GReader API is not official, but I just want to make sure that OAuth >> >>>>>> won't go away all of a sudden) >> >>>>>> Thanks again for the OAuth support. >> >>>>>> -- >> >>>>>> Jayesh
>> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi >> >>>>>> <jayeshsa...@gmail.com> wrote:
>> >>>>>>> -- >> >>>>>>> Jayesh
>> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes <bhaw...@google.com> >> >>>>>>> wrote:
>> >>>>>>>> It will work for reader/atom/* . It doesn't however work for >> >>>>>>>> subscriptions/export . If this is a problem I can see about getting it >> >>>>>>>> added.
>> >>>>>>> It will be great if it would work for subscriptions/export, I >> >>>>>>> think many clients use OPML export. >> >>>>>>> I will try to test the new OAuth later today. >> >>>>>>> Thanks for quick reply.
>> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi >> >>>>>>>> <jayeshsa...@gmail.com> wrote:
>> >>>>>>>>> -- >> >>>>>>>>> Jayesh
>> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes >> >>>>>>>>> <bhaw...@google.com> wrote:
>> >>>>>>>>>> Hello friends, >> >>>>>>>>>> It was asked in a previous thread if we could provide OAuth >> >>>>>>>>>> capabilities for accessing Reader data. We recently enabled OAuth support >> >>>>>>>>>> for Reader. You can find relevant information >> >>>>>>>>>> here: http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
>> >>>>>>>>> Awesome. If this works, it will be the best solution to get user >> >>>>>>>>> logged in w/o username/password.
>> >>>>>>>>> To unsubscribe from this group, send email to >> >>>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with the words >> >>>>>>>>> "REMOVE ME" as the subject.
>> >>>>>>>> To unsubscribe from this group, send email to >> >>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with the words >> >>>>>>>> "REMOVE ME" as the subject.
>> >>>>>> To unsubscribe from this group, send email to >> >>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with the words >> >>>>>> "REMOVE ME" as the subject.
>> >>>>> To unsubscribe from this group, send email to >> >>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with the words >> >>>>> "REMOVE ME" as the subject.
> >> > Please let me know if you find something wrong about these end points > >> > on google reader side. > >> > -- > >> > Jayesh
> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi <jayeshsa...@gmail.com> > >> > wrote: > >> >> Hi Brad, > >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized with > >> >> OAuth.
> >> >>>> Let me know. > >> >>>> Thanks > >> >>>> -- > >> >>>> Jayesh
> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> > >> >>>> wrote:
> >> >>>>> I have enabled OAuth on the subscription export so you should be > >> >>>>> able to use that as well now. > >> >>>>> I can't say definitively what Google is going to do with respect > to > >> >>>>> auth systems, however OAuth is not experimental, I fully expect > its support > >> >>>>> to outlast ClientLogin. We actually prefer OAuth to ClientLogin > now so that > >> >>>>> users don't have to provide Google credentials to third party > applications. > >> >>>>> -Brad > >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi > >> >>>>> <jayeshsa...@gmail.com> wrote:
> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least for > >> >>>>>> subscription list). > >> >>>>>> Here is example code: > >> >>>>>> http://pastebin.com/VbusAELq > >> >>>>>> It uses SignPost for OAuth. It's generic java code run from > >> >>>>>> desktop, but can be used for Android with some modifications. > >> >>>>>> I am yet to test all calls to make sure they work with OAuth, but > >> >>>>>> this is a good start. > >> >>>>>> Brad, could you enable OAuth on subscriptions/export request? My > >> >>>>>> android app (ReaderScope) uses it to download OPML data. > >> >>>>>> Also, one question to Google Reader team. Is the OAuth support an > >> >>>>>> experiment or can I start using it in real world and deploy it in > my app? (I > >> >>>>>> know GReader API is not official, but I just want to make sure > that OAuth > >> >>>>>> won't go away all of a sudden) > >> >>>>>> Thanks again for the OAuth support. > >> >>>>>> -- > >> >>>>>> Jayesh
> >> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi > >> >>>>>> <jayeshsa...@gmail.com> wrote:
> >> >>>>>>> -- > >> >>>>>>> Jayesh
> >> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes < > bhaw...@google.com> > >> >>>>>>> wrote:
> >> >>>>>>>> It will work for reader/atom/* . It doesn't however work for > >> >>>>>>>> subscriptions/export . If this is a problem I can see about > getting it > >> >>>>>>>> added.
> >> >>>>>>> It will be great if it would work for subscriptions/export, I > >> >>>>>>> think many clients use OPML export. > >> >>>>>>> I will try to test the new OAuth later today. > >> >>>>>>> Thanks for quick reply.
> >> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi > >> >>>>>>>> <jayeshsa...@gmail.com> wrote:
> >> >>>>>>>>> -- > >> >>>>>>>>> Jayesh
> >> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes > >> >>>>>>>>> <bhaw...@google.com> wrote:
> >> >>>>>>>>>> Hello friends, > >> >>>>>>>>>> It was asked in a previous thread if we could provide OAuth > >> >>>>>>>>>> capabilities for accessing Reader data. We recently enabled > OAuth support > >> >>>>>>>>>> for Reader. You can find relevant information > >> >>>>>>>>>> here: > http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html
> >> >>>>>>>>> Awesome. If this works, it will be the best solution to get > user > >> >>>>>>>>> logged in w/o username/password.
> >> >>>>>>>>> To unsubscribe from this group, send email to > >> >>>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email > with the words > >> >>>>>>>>> "REMOVE ME" as the subject.
> >> >>>>>>>> To unsubscribe from this group, send email to > >> >>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email > with the words > >> >>>>>>>> "REMOVE ME" as the subject.
> >> >>>>>> To unsubscribe from this group, send email to > >> >>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with > the words > >> >>>>>> "REMOVE ME" as the subject.
> >> >>>>> To unsubscribe from this group, send email to > >> >>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with > the words > >> >>>>> "REMOVE ME" as the subject.
On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> wrote: > Are you providing the T action token? That's still required even with OAuth.
Yes I am doing that. My code is unchanged except for OAuth signing at lower level, so I am adding POST params just like before, including the Token.
>> >> > Please let me know if you find something wrong about these end points >> >> > on google reader side. >> >> > -- >> >> > Jayesh
>> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi <jayeshsa...@gmail.com> >> >> > wrote: >> >> >> Hi Brad, >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized with >> >> >> OAuth.
>> >> >>>> Let me know. >> >> >>>> Thanks >> >> >>>> -- >> >> >>>> Jayesh
>> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes <bhaw...@google.com> >> >> >>>> wrote:
>> >> >>>>> I have enabled OAuth on the subscription export so you should be >> >> >>>>> able to use that as well now. >> >> >>>>> I can't say definitively what Google is going to do with respect >> >> >>>>> to >> >> >>>>> auth systems, however OAuth is not experimental, I fully expect >> >> >>>>> its support >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to ClientLogin >> >> >>>>> now so that >> >> >>>>> users don't have to provide Google credentials to third party >> >> >>>>> applications. >> >> >>>>> -Brad >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi >> >> >>>>> <jayeshsa...@gmail.com> wrote:
>> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least for >> >> >>>>>> subscription list). >> >> >>>>>> Here is example code: >> >> >>>>>> http://pastebin.com/VbusAELq >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run from >> >> >>>>>> desktop, but can be used for Android with some modifications. >> >> >>>>>> I am yet to test all calls to make sure they work with OAuth, >> >> >>>>>> but >> >> >>>>>> this is a good start. >> >> >>>>>> Brad, could you enable OAuth on subscriptions/export request? My >> >> >>>>>> android app (ReaderScope) uses it to download OPML data. >> >> >>>>>> Also, one question to Google Reader team. Is the OAuth support >> >> >>>>>> an >> >> >>>>>> experiment or can I start using it in real world and deploy it >> >> >>>>>> in my app? (I >> >> >>>>>> know GReader API is not official, but I just want to make sure >> >> >>>>>> that OAuth >> >> >>>>>> won't go away all of a sudden) >> >> >>>>>> Thanks again for the OAuth support. >> >> >>>>>> -- >> >> >>>>>> Jayesh
>> >> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi >> >> >>>>>> <jayeshsa...@gmail.com> wrote:
>> >> >>>>>>> -- >> >> >>>>>>> Jayesh
>> >> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes >> >> >>>>>>> <bhaw...@google.com> >> >> >>>>>>> wrote:
>> >> >>>>>>>> It will work for reader/atom/* . It doesn't however work for >> >> >>>>>>>> subscriptions/export . If this is a problem I can see about >> >> >>>>>>>> getting it >> >> >>>>>>>> added.
>> >> >>>>>>> It will be great if it would work for subscriptions/export, I >> >> >>>>>>> think many clients use OPML export. >> >> >>>>>>> I will try to test the new OAuth later today. >> >> >>>>>>> Thanks for quick reply.
>> >> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi >> >> >>>>>>>> <jayeshsa...@gmail.com> wrote:
>> >> >>>>>>>>> -- >> >> >>>>>>>>> Jayesh
>> >> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes >> >> >>>>>>>>> <bhaw...@google.com> wrote:
>> >> >>>>>>>>>> Hello friends, >> >> >>>>>>>>>> It was asked in a previous thread if we could provide OAuth >> >> >>>>>>>>>> capabilities for accessing Reader data. We recently enabled >> >> >>>>>>>>>> OAuth support >> >> >>>>>>>>>> for Reader. You can find relevant information
>> >> >>>>>>>>> To unsubscribe from this group, send email to >> >> >>>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email >> >> >>>>>>>>> with the words >> >> >>>>>>>>> "REMOVE ME" as the subject.
>> >> >>>>>>>> To unsubscribe from this group, send email to >> >> >>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email >> >> >>>>>>>> with the words >> >> >>>>>>>> "REMOVE ME" as the subject.
>> >> >>>>>> To unsubscribe from this group, send email to >> >> >>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with >> >> >>>>>> the words >> >> >>>>>> "REMOVE ME" as the subject.
>> >> >>>>> To unsubscribe from this group, send email to >> >> >>>>> fougrapi+unsubscribegooglegroups.com or reply to this email with >> >> >>>>> the words >> >> >>>>> "REMOVE ME" as the subject.
Jayesh, OAuth is supported by our authentication library natively. I just enabled it on the various paths mentioned including edit-tag . It would probably be good to verify that you are correctly encoding the POST variables into the OAuth base signature string.
On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > -- > Jayesh
> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> > wrote: > > Are you providing the T action token? That's still required even with > OAuth.
> Yes I am doing that. My code is unchanged except for OAuth signing at > lower level, so I am adding POST params just like before, including > the Token.
> > Mihai
> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi <jayeshsa...@gmail.com> > > wrote:
> >> I checked again. It seems it IS failing for many POST requests, except > for > >> one.
> >> The POST requests to "api/0/stream/items/contents" are successful.
> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", > >> "api/0/edit-tag" fail. > >> -- > >> Jayesh
> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita <mih...@google.com> > >> wrote: > >> > Is it all POST requests that fail, or just those to edit-tag?
> >> > Mihai
> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi <jayeshsa...@gmail.com> > >> > wrote:
> >> >> ping! any news on this one?
> >> >> Thanks. > >> >> -- > >> >> Jayesh
> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi < > jayeshsa...@gmail.com> > >> >> wrote: > >> >> > Hi Brad,
> >> >> > I think I have tested all the endpoints so far and except for the > two > >> >> > all others are working.
> >> >> > The failing ones are edit-tags and subscriptions/export.
> >> >> > Please let me know if you find something wrong about these end > points > >> >> > on google reader side. > >> >> > -- > >> >> > Jayesh
> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi < > jayeshsa...@gmail.com> > >> >> > wrote: > >> >> >> Hi Brad, > >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized with > >> >> >> OAuth.
> >> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes < > bhaw...@google.com> > >> >> >>>> wrote:
> >> >> >>>>> I have enabled OAuth on the subscription export so you should > be > >> >> >>>>> able to use that as well now. > >> >> >>>>> I can't say definitively what Google is going to do with > respect > >> >> >>>>> to > >> >> >>>>> auth systems, however OAuth is not experimental, I fully expect > >> >> >>>>> its support > >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to ClientLogin > >> >> >>>>> now so that > >> >> >>>>> users don't have to provide Google credentials to third party > >> >> >>>>> applications. > >> >> >>>>> -Brad > >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi > >> >> >>>>> <jayeshsa...@gmail.com> wrote:
> >> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least for > >> >> >>>>>> subscription list). > >> >> >>>>>> Here is example code: > >> >> >>>>>> http://pastebin.com/VbusAELq > >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run from > >> >> >>>>>> desktop, but can be used for Android with some modifications. > >> >> >>>>>> I am yet to test all calls to make sure they work with OAuth, > >> >> >>>>>> but > >> >> >>>>>> this is a good start. > >> >> >>>>>> Brad, could you enable OAuth on subscriptions/export request? > My > >> >> >>>>>> android app (ReaderScope) uses it to download OPML data. > >> >> >>>>>> Also, one question to Google Reader team. Is the OAuth support > >> >> >>>>>> an > >> >> >>>>>> experiment or can I start using it in real world and deploy it > >> >> >>>>>> in my app? (I > >> >> >>>>>> know GReader API is not official, but I just want to make sure > >> >> >>>>>> that OAuth > >> >> >>>>>> won't go away all of a sudden) > >> >> >>>>>> Thanks again for the OAuth support. > >> >> >>>>>> -- > >> >> >>>>>> Jayesh
> >> >> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi > >> >> >>>>>> <jayeshsa...@gmail.com> wrote:
> >> >> >>>>>>> -- > >> >> >>>>>>> Jayesh
> >> >> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes > >> >> >>>>>>> <bhaw...@google.com> > >> >> >>>>>>> wrote:
> >> >> >>>>>>>> It will work for reader/atom/* . It doesn't however work for > >> >> >>>>>>>> subscriptions/export . If this is a problem I can see about > >> >> >>>>>>>> getting it > >> >> >>>>>>>> added.
> >> >> >>>>>>> It will be great if it would work for subscriptions/export, I > >> >> >>>>>>> think many clients use OPML export. > >> >> >>>>>>> I will try to test the new OAuth later today. > >> >> >>>>>>> Thanks for quick reply.
> >> >> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi > >> >> >>>>>>>> <jayeshsa...@gmail.com> wrote:
> >> >> >>>>>>>>> -- > >> >> >>>>>>>>> Jayesh
> >> >> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes > >> >> >>>>>>>>> <bhaw...@google.com> wrote:
> >> >> >>>>>>>>>> Hello friends, > >> >> >>>>>>>>>> It was asked in a previous thread if we could provide > OAuth > >> >> >>>>>>>>>> capabilities for accessing Reader data. We recently > enabled > >> >> >>>>>>>>>> OAuth support > >> >> >>>>>>>>>> for Reader. You can find relevant information
> >> >> >>>>>>>>> Awesome. If this works, it will be the best solution to get > >> >> >>>>>>>>> user > >> >> >>>>>>>>> logged in w/o username/password.
> >> >> >>>>>>>>> To unsubscribe from this group, send email to > >> >> >>>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this > email > >> >> >>>>>>>>> with the words > >> >> >>>>>>>>> "REMOVE ME" as the subject.
> >> >> >>>>>>>> To unsubscribe from this group, send email to > >> >> >>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email > >> >> >>>>>>>> with the words > >> >> >>>>>>>> "REMOVE ME" as the subject.
> >> >> >>>>>> To unsubscribe from this group, send email to > >> >> >>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email > with > >> >> >>>>>> the words > >> >> >>>>>> "REMOVE ME" as the subject.
> >> >> >>>>> To unsubscribe from this group, send email to > >> >> >>>>> fougrapi+unsubscribegooglegroups.com or reply to this email > with > >> >> >>>>> the words > >> >> >>>>> "REMOVE ME" as the subject.
On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> wrote: > Jayesh, > OAuth is supported by our authentication library natively. I just enabled it > on the various paths mentioned including edit-tag .
Could you tell me which client library did you use to test (if it is publicly available)? I can recheck my code against it. I am using SignPost, which apparently seems to be a standard OAuth library, but I will check.
> It would probably be > good to verify that you are correctly encoding the POST variables into the > OAuth base signature string. > -Brad > On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>> -- >> Jayesh
>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> >> wrote: >> > Are you providing the T action token? That's still required even with >> > OAuth.
>> Yes I am doing that. My code is unchanged except for OAuth signing at >> lower level, so I am adding POST params just like before, including >> the Token.
>> > Mihai
>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi <jayeshsa...@gmail.com> >> > wrote:
>> >> I checked again. It seems it IS failing for many POST requests, except >> >> for >> >> one.
>> >> The POST requests to "api/0/stream/items/contents" are successful.
>> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", >> >> "api/0/edit-tag" fail. >> >> -- >> >> Jayesh
>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita <mih...@google.com> >> >> wrote: >> >> > Is it all POST requests that fail, or just those to edit-tag?
>> >> > Mihai
>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi <jayeshsa...@gmail.com> >> >> > wrote:
>> >> >> ping! any news on this one?
>> >> >> Thanks. >> >> >> -- >> >> >> Jayesh
>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi >> >> >> <jayeshsa...@gmail.com> >> >> >> wrote: >> >> >> > Hi Brad,
>> >> >> > I think I have tested all the endpoints so far and except for the >> >> >> > two >> >> >> > all others are working.
>> >> >> > The failing ones are edit-tags and subscriptions/export.
>> >> >> > Please let me know if you find something wrong about these end >> >> >> > points >> >> >> > on google reader side. >> >> >> > -- >> >> >> > Jayesh
>> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi >> >> >> > <jayeshsa...@gmail.com> >> >> >> > wrote: >> >> >> >> Hi Brad, >> >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized >> >> >> >> with >> >> >> >> OAuth.
>> >> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes >> >> >> >>>> <bhaw...@google.com> >> >> >> >>>> wrote:
>> >> >> >>>>> I have enabled OAuth on the subscription export so you should >> >> >> >>>>> be >> >> >> >>>>> able to use that as well now. >> >> >> >>>>> I can't say definitively what Google is going to do with >> >> >> >>>>> respect >> >> >> >>>>> to >> >> >> >>>>> auth systems, however OAuth is not experimental, I fully >> >> >> >>>>> expect >> >> >> >>>>> its support >> >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to >> >> >> >>>>> ClientLogin >> >> >> >>>>> now so that >> >> >> >>>>> users don't have to provide Google credentials to third party >> >> >> >>>>> applications. >> >> >> >>>>> -Brad >> >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi >> >> >> >>>>> <jayeshsa...@gmail.com> wrote:
>> >> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least for >> >> >> >>>>>> subscription list). >> >> >> >>>>>> Here is example code: >> >> >> >>>>>> http://pastebin.com/VbusAELq >> >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run from >> >> >> >>>>>> desktop, but can be used for Android with some modifications. >> >> >> >>>>>> I am yet to test all calls to make sure they work with OAuth, >> >> >> >>>>>> but >> >> >> >>>>>> this is a good start. >> >> >> >>>>>> Brad, could you enable OAuth on subscriptions/export request? >> >> >> >>>>>> My >> >> >> >>>>>> android app (ReaderScope) uses it to download OPML data. >> >> >> >>>>>> Also, one question to Google Reader team. Is the OAuth >> >> >> >>>>>> support >> >> >> >>>>>> an >> >> >> >>>>>> experiment or can I start using it in real world and deploy >> >> >> >>>>>> it >> >> >> >>>>>> in my app? (I >> >> >> >>>>>> know GReader API is not official, but I just want to make >> >> >> >>>>>> sure >> >> >> >>>>>> that OAuth >> >> >> >>>>>> won't go away all of a sudden) >> >> >> >>>>>> Thanks again for the OAuth support. >> >> >> >>>>>> -- >> >> >> >>>>>> Jayesh
>> >> >> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi >> >> >> >>>>>> <jayeshsa...@gmail.com> wrote:
>> >> >> >>>>>>> -- >> >> >> >>>>>>> Jayesh
>> >> >> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes >> >> >> >>>>>>> <bhaw...@google.com> >> >> >> >>>>>>> wrote:
>> >> >> >>>>>>>> It will work for reader/atom/* . It doesn't however work >> >> >> >>>>>>>> for >> >> >> >>>>>>>> subscriptions/export . If this is a problem I can see about >> >> >> >>>>>>>> getting it >> >> >> >>>>>>>> added.
>> >> >> >>>>>>> It will be great if it would work for subscriptions/export, >> >> >> >>>>>>> I >> >> >> >>>>>>> think many clients use OPML export. >> >> >> >>>>>>> I will try to test the new OAuth later today. >> >> >> >>>>>>> Thanks for quick reply.
>> >> >> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi >> >> >> >>>>>>>> <jayeshsa...@gmail.com> wrote:
>> >> >> >>>>>>>>> -- >> >> >> >>>>>>>>> Jayesh
>> >> >> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes >> >> >> >>>>>>>>> <bhaw...@google.com> wrote:
>> >> >> >>>>>>>>>> Hello friends, >> >> >> >>>>>>>>>> It was asked in a previous thread if we could provide >> >> >> >>>>>>>>>> OAuth >> >> >> >>>>>>>>>> capabilities for accessing Reader data. We recently >> >> >> >>>>>>>>>> enabled >> >> >> >>>>>>>>>> OAuth support >> >> >> >>>>>>>>>> for Reader. You can find relevant information
>> >> >> >>>>>>>>> Awesome. If this works, it will be the best solution to >> >> >> >>>>>>>>> get >> >> >> >>>>>>>>> user >> >> >> >>>>>>>>> logged in w/o username/password.
>> >> >> >>>>>>>>> To unsubscribe from this group, send email to >> >> >> >>>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this >> >> >> >>>>>>>>> email >> >> >> >>>>>>>>> with the words >> >> >> >>>>>>>>> "REMOVE ME" as the subject.
>> >> >> >>>>>>>> To unsubscribe from this group, send email to >> >> >> >>>>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email >> >> >> >>>>>>>> with the words >> >> >> >>>>>>>> "REMOVE ME" as the subject.
>> >> >> >>>>>> To unsubscribe from this group, send email to >> >> >> >>>>>> fougrapi+unsubscribegooglegroups.com or reply to this email >> >> >> >>>>>> with >> >> >> >>>>>> the words >> >> >> >>>>>> "REMOVE ME" as the subject.
>> >> >> >>>>> To unsubscribe from this group, send email to >> >> >> >>>>> fougrapi+unsubscribegooglegroups.com or reply to this email >> >> >> >>>>> with >> >> >> >>>>> the words >> >> >> >>>>> "REMOVE ME" as the subject.
I analysed the java SignPost library I was using and dumped the post params/ signature base string etc. But couldn't find anything useful.
I also tried couple of python libraries to get more sample points, but couldn't get those libraries beyond getRequestToken. They all are well tested for Twitter, but can't seem to handle the "scope" post param required for Google oauth.
IIRC, you guys can lookup the requests in server logs based on User Agent strings. Do you think you can tell me if you find something there? I ran the test that marks an item read about 5-10 min ago, with the SOURCE http header set to "ReaderScope 1.8.5x". I got 401-Unauthorized for an edit-tag method invocation. Can Google Reader log tell what in particular went wrong in that request? There should be only one request with that SOURCE field, so it should be easily searchable provided it is kept in logs.
It's difficult at the client side, because there are many things that can go wrong in signing the OAuth request properly. It doesn't help that server returns same error code for all of those errors (401).
Let me know if you can help or have any more suggestions.
On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> wrote: >> Jayesh, >> OAuth is supported by our authentication library natively. I just enabled it >> on the various paths mentioned including edit-tag .
> Could you tell me which client library did you use to test (if it is > publicly available)? I can recheck my code against it. > I am using SignPost, which apparently seems to be a standard OAuth > library, but I will check.
>> It would probably be >> good to verify that you are correctly encoding the POST variables into the >> OAuth base signature string. >> -Brad >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>> -- >>> Jayesh
>>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> >>> wrote: >>> > Are you providing the T action token? That's still required even with >>> > OAuth.
>>> Yes I am doing that. My code is unchanged except for OAuth signing at >>> lower level, so I am adding POST params just like before, including >>> the Token.
>>> > Mihai
>>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi <jayeshsa...@gmail.com> >>> > wrote:
>>> >> I checked again. It seems it IS failing for many POST requests, except >>> >> for >>> >> one.
>>> >> The POST requests to "api/0/stream/items/contents" are successful.
>>> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", >>> >> "api/0/edit-tag" fail. >>> >> -- >>> >> Jayesh
>>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita <mih...@google.com> >>> >> wrote: >>> >> > Is it all POST requests that fail, or just those to edit-tag?
>>> >> > Mihai
>>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi <jayeshsa...@gmail.com> >>> >> > wrote:
>>> >> >> ping! any news on this one?
>>> >> >> Thanks. >>> >> >> -- >>> >> >> Jayesh
>>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi >>> >> >> <jayeshsa...@gmail.com> >>> >> >> wrote: >>> >> >> > Hi Brad,
>>> >> >> > I think I have tested all the endpoints so far and except for the >>> >> >> > two >>> >> >> > all others are working.
>>> >> >> > The failing ones are edit-tags and subscriptions/export.
>>> >> >> > Please let me know if you find something wrong about these end >>> >> >> > points >>> >> >> > on google reader side. >>> >> >> > -- >>> >> >> > Jayesh
>>> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi >>> >> >> > <jayeshsa...@gmail.com> >>> >> >> > wrote: >>> >> >> >> Hi Brad, >>> >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized >>> >> >> >> with >>> >> >> >> OAuth.
>>> >> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes >>> >> >> >>>> <bhaw...@google.com> >>> >> >> >>>> wrote:
>>> >> >> >>>>> I have enabled OAuth on the subscription export so you should >>> >> >> >>>>> be >>> >> >> >>>>> able to use that as well now. >>> >> >> >>>>> I can't say definitively what Google is going to do with >>> >> >> >>>>> respect >>> >> >> >>>>> to >>> >> >> >>>>> auth systems, however OAuth is not experimental, I fully >>> >> >> >>>>> expect >>> >> >> >>>>> its support >>> >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to >>> >> >> >>>>> ClientLogin >>> >> >> >>>>> now so that >>> >> >> >>>>> users don't have to provide Google credentials to third party >>> >> >> >>>>> applications. >>> >> >> >>>>> -Brad >>> >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi >>> >> >> >>>>> <jayeshsa...@gmail.com> wrote:
>>> >> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least for >>> >> >> >>>>>> subscription list). >>> >> >> >>>>>> Here is example code: >>> >> >> >>>>>> http://pastebin.com/VbusAELq >>> >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run from >>> >> >> >>>>>> desktop, but can be used for Android with some modifications. >>> >> >> >>>>>> I am yet to test all calls to make sure they work with OAuth, >>> >> >> >>>>>> but >>> >> >> >>>>>> this is a good start. >>> >> >> >>>>>> Brad, could you enable OAuth on subscriptions/export request? >>> >> >> >>>>>> My >>> >> >> >>>>>> android app (ReaderScope) uses it to download OPML data. >>> >> >> >>>>>> Also, one question to Google Reader team. Is the OAuth >>> >> >> >>>>>> support >>> >> >> >>>>>> an >>> >> >> >>>>>> experiment or can I start using it in real world and deploy >>> >> >> >>>>>> it >>> >> >> >>>>>> in my app? (I >>> >> >> >>>>>> know GReader API is not official, but I just want to make >>> >> >> >>>>>> sure >>> >> >> >>>>>> that OAuth >>> >> >> >>>>>> won't go away all of a sudden) >>> >> >> >>>>>> Thanks again for the OAuth support. >>> >> >> >>>>>> -- >>> >> >> >>>>>> Jayesh
>>> >> >> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi >>> >> >> >>>>>> <jayeshsa...@gmail.com> wrote:
>>> >> >> >>>>>>> -- >>> >> >> >>>>>>> Jayesh
>>> >> >> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes >>> >> >> >>>>>>> <bhaw...@google.com> >>> >> >> >>>>>>> wrote:
>>> >> >> >>>>>>>> It will work for reader/atom/* . It doesn't however work >>> >> >> >>>>>>>> for >>> >> >> >>>>>>>> subscriptions/export . If this is a problem I can see about >>> >> >> >>>>>>>> getting it >>> >> >> >>>>>>>> added.
>>> >> >> >>>>>>> It will be great if it would work for subscriptions/export, >>> >> >> >>>>>>> I >>> >> >> >>>>>>> think many clients use OPML export. >>> >> >> >>>>>>> I will try to test the new OAuth later today. >>> >> >> >>>>>>> Thanks for quick reply.
>>> >> >> >>>>>>>> On Mon, Mar 22, 2010 at 7:56 PM, Jayesh Salvi >>> >> >> >>>>>>>> <jayeshsa...@gmail.com> wrote:
>>> >> >> >>>>>>>>> -- >>> >> >> >>>>>>>>> Jayesh
>>> >> >> >>>>>>>>> On Tue, Mar 23, 2010 at 7:27 AM, Brad Hawkes >>> >> >> >>>>>>>>> <bhaw...@google.com> wrote:
>>> >> >> >>>>>>>>>> Hello friends, >>> >> >> >>>>>>>>>> It was asked in a previous thread if we could provide >>> >> >> >>>>>>>>>> OAuth >>> >> >> >>>>>>>>>> capabilities for accessing Reader data. We recently >>> >> >> >>>>>>>>>> enabled >>> >> >> >>>>>>>>>> OAuth support >>> >> >> >>>>>>>>>> for Reader. You can find relevant information
>>> >> >> >>>>>>>>> Awesome. If this works, it will be the best solution to >>> >> >> >>>>>>>>> get >>> >> >> >>>>>>>>> user >>> >> >> >>>>>>>>> logged in w/o username/password.
When using HttpURLConnection, you cannot sign POST requests that carry query parameters in the message payload (i.e. requests of type application/x-www-form-urlencoded). This is not a limitation of Signpost per se, but with the way URLConnection works. Server communication with URLConnection is based on data streams, which means that whenever you write something to the connection, it will be sent to the server immediately. This data is not buffered, and there is simply no way for Signpost to inspect that data and include it in a signature. Hence, when you have to sign requests which contain parameters in their body, you have to use an HTTP library like Apache Commons HttpComponents and the respective Signpost module. (This restriction does not apply to requests which send binary data such as documents or files, because that data won't become part of the signature anyway.)
On Thu, Apr 1, 2010 at 11:52 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > Hi guys,
> I tried all I could think of, but no help.
> I analysed the java SignPost library I was using and dumped the post > params/ signature base string etc. But couldn't find anything useful.
> I also tried couple of python libraries to get more sample points, but > couldn't get those libraries beyond getRequestToken. They all are well > tested for Twitter, but can't seem to handle the "scope" post param > required for Google oauth.
> IIRC, you guys can lookup the requests in server logs based on User > Agent strings. Do you think you can tell me if you find something > there? I ran the test that marks an item read about 5-10 min ago, with > the SOURCE http header set to "ReaderScope 1.8.5x". I got > 401-Unauthorized for an edit-tag method invocation. Can Google Reader > log tell what in particular went wrong in that request? There should > be only one request with that SOURCE field, so it should be easily > searchable provided it is kept in logs.
> It's difficult at the client side, because there are many things that > can go wrong in signing the OAuth request properly. It doesn't help > that server returns same error code for all of those errors (401).
> Let me know if you can help or have any more suggestions.
> Thanks. > -- > Jayesh
> On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com> > wrote: > > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> > wrote: > >> Jayesh, > >> OAuth is supported by our authentication library natively. I just > enabled it > >> on the various paths mentioned including edit-tag .
> > Could you tell me which client library did you use to test (if it is > > publicly available)? I can recheck my code against it. > > I am using SignPost, which apparently seems to be a standard OAuth > > library, but I will check.
> >> It would probably be > >> good to verify that you are correctly encoding the POST variables into > the > >> OAuth base signature string. > >> -Brad > >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> > wrote:
> >>> -- > >>> Jayesh
> >>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> > >>> wrote: > >>> > Are you providing the T action token? That's still required even with > >>> > OAuth.
> >>> Yes I am doing that. My code is unchanged except for OAuth signing at > >>> lower level, so I am adding POST params just like before, including > >>> the Token.
> >>> > Mihai
> >>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi < > jayeshsa...@gmail.com> > >>> > wrote:
> >>> >> I checked again. It seems it IS failing for many POST requests, > except > >>> >> for > >>> >> one.
> >>> >> The POST requests to "api/0/stream/items/contents" are successful.
> >>> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", > >>> >> "api/0/edit-tag" fail. > >>> >> -- > >>> >> Jayesh
> >>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita <mih...@google.com
> >>> >> wrote: > >>> >> > Is it all POST requests that fail, or just those to edit-tag?
> >>> >> > Mihai
> >>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi < > jayeshsa...@gmail.com> > >>> >> > wrote:
> >>> >> >> > Please let me know if you find something wrong about these end > >>> >> >> > points > >>> >> >> > on google reader side. > >>> >> >> > -- > >>> >> >> > Jayesh
> >>> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi > >>> >> >> > <jayeshsa...@gmail.com> > >>> >> >> > wrote: > >>> >> >> >> Hi Brad, > >>> >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized > >>> >> >> >> with > >>> >> >> >> OAuth.
> >>> >> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes > >>> >> >> >>>> <bhaw...@google.com> > >>> >> >> >>>> wrote:
> >>> >> >> >>>>> I have enabled OAuth on the subscription export so you > should > >>> >> >> >>>>> be > >>> >> >> >>>>> able to use that as well now. > >>> >> >> >>>>> I can't say definitively what Google is going to do with > >>> >> >> >>>>> respect > >>> >> >> >>>>> to > >>> >> >> >>>>> auth systems, however OAuth is not experimental, I fully > >>> >> >> >>>>> expect > >>> >> >> >>>>> its support > >>> >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to > >>> >> >> >>>>> ClientLogin > >>> >> >> >>>>> now so that > >>> >> >> >>>>> users don't have to provide Google credentials to third > party > >>> >> >> >>>>> applications. > >>> >> >> >>>>> -Brad > >>> >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi > >>> >> >> >>>>> <jayeshsa...@gmail.com> wrote:
> >>> >> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least > for > >>> >> >> >>>>>> subscription list). > >>> >> >> >>>>>> Here is example code: > >>> >> >> >>>>>> http://pastebin.com/VbusAELq > >>> >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run > from > >>> >> >> >>>>>> desktop, but can be used for Android with some > modifications. > >>> >> >> >>>>>> I am yet to test all calls to make sure they work with > OAuth, > >>> >> >> >>>>>> but > >>> >> >> >>>>>> this is a good start. > >>> >> >> >>>>>> Brad, could you enable OAuth on subscriptions/export > request? > >>> >> >> >>>>>> My > >>> >> >> >>>>>> android app (ReaderScope) uses it to download OPML data. > >>> >> >> >>>>>> Also, one question to Google Reader team. Is the OAuth > >>> >> >> >>>>>> support > >>> >> >> >>>>>> an > >>> >> >> >>>>>> experiment or can I start using it in real world and > deploy > >>> >> >> >>>>>> it > >>> >> >> >>>>>> in my app? (I > >>> >> >> >>>>>> know GReader API is not official, but I just want to make > >>> >> >> >>>>>> sure > >>> >> >> >>>>>> that OAuth > >>> >> >> >>>>>> won't go away all of a sudden) > >>> >> >> >>>>>> Thanks again for the OAuth support. > >>> >> >> >>>>>> -- > >>> >> >> >>>>>> Jayesh
> >>> >> >> >>>>>> On Tue, Mar 23, 2010 at 8:39 AM, Jayesh Salvi > >>> >> >> >>>>>> <jayeshsa...@gmail.com> wrote:
> >>> >> >> >>>>>>> -- > >>> >> >> >>>>>>> Jayesh
> >>> >> >> >>>>>>> On Tue, Mar 23, 2010 at 8:35 AM, Brad Hawkes > >>> >> >> >>>>>>> <bhaw...@google.com> > >>> >> >> >>>>>>> wrote:
> >>> >> >> >>>>>>>> It will work for reader/atom/* . It doesn't however work > >>> >> >> >>>>>>>> for > >>> >> >> >>>>>>>> subscriptions/export . If this is a problem I can see > about > >>> >> >> >>>>>>>> getting it > >>> >> >> >>>>>>>> added.
> >>> >> >> >>>>>>> It will be great if it would work for > subscriptions/export,
On Fri, Apr 2, 2010 at 1:58 AM, Brad Hawkes <bhaw...@google.com> wrote: > Hi Jayesh, > I looked up your request and it was indeed an error due to an invalid > signature. > I think the problem you are having is a known issue with SignPost. > From http://code.google.com/p/oauth-signpost/wiki/GettingStarted : > When using HttpURLConnection, you cannot sign POST requests that carry query > parameters in the message payload (i.e. requests of type > application/x-www-form-urlencoded). This is not a limitation of Signpost per > se, but with the way URLConnection works. Server communication with > URLConnection is based on data streams, which means that whenever you write > something to the connection, it will be sent to the server immediately. This > data is not buffered, and there is simply no way for Signpost to inspect > that data and include it in a signature. Hence, when you have to sign > requests which contain parameters in their body, you have to use an HTTP > library like Apache Commons HttpComponents and the respective Signpost > module. (This restriction does not apply to requests which send binary data > such as documents or files, because that data won't become part of the > signature anyway.) > -Brad
Thanks a bunch Brad. That seems to explain it. I will try the suggestions later today and report what I find.
> On Thu, Apr 1, 2010 at 11:52 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>> Hi guys,
>> I tried all I could think of, but no help.
>> I analysed the java SignPost library I was using and dumped the post >> params/ signature base string etc. But couldn't find anything useful.
>> I also tried couple of python libraries to get more sample points, but >> couldn't get those libraries beyond getRequestToken. They all are well >> tested for Twitter, but can't seem to handle the "scope" post param >> required for Google oauth.
>> IIRC, you guys can lookup the requests in server logs based on User >> Agent strings. Do you think you can tell me if you find something >> there? I ran the test that marks an item read about 5-10 min ago, with >> the SOURCE http header set to "ReaderScope 1.8.5x". I got >> 401-Unauthorized for an edit-tag method invocation. Can Google Reader >> log tell what in particular went wrong in that request? There should >> be only one request with that SOURCE field, so it should be easily >> searchable provided it is kept in logs.
>> It's difficult at the client side, because there are many things that >> can go wrong in signing the OAuth request properly. It doesn't help >> that server returns same error code for all of those errors (401).
>> Let me know if you can help or have any more suggestions.
>> Thanks. >> -- >> Jayesh
>> On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com> >> wrote: >> > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> >> > wrote: >> >> Jayesh, >> >> OAuth is supported by our authentication library natively. I just >> >> enabled it >> >> on the various paths mentioned including edit-tag .
>> > Could you tell me which client library did you use to test (if it is >> > publicly available)? I can recheck my code against it. >> > I am using SignPost, which apparently seems to be a standard OAuth >> > library, but I will check.
>> >> It would probably be >> >> good to verify that you are correctly encoding the POST variables into >> >> the >> >> OAuth base signature string. >> >> -Brad >> >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> >> >> wrote:
>> >>> -- >> >>> Jayesh
>> >>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> >> >>> wrote: >> >>> > Are you providing the T action token? That's still required even >> >>> > with >> >>> > OAuth.
>> >>> Yes I am doing that. My code is unchanged except for OAuth signing at >> >>> lower level, so I am adding POST params just like before, including >> >>> the Token.
>> >>> > Mihai
>> >>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi >> >>> > <jayeshsa...@gmail.com> >> >>> > wrote:
>> >>> >> I checked again. It seems it IS failing for many POST requests, >> >>> >> except >> >>> >> for >> >>> >> one.
>> >>> >> The POST requests to "api/0/stream/items/contents" are successful.
>> >>> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", >> >>> >> "api/0/edit-tag" fail. >> >>> >> -- >> >>> >> Jayesh
>> >>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita >> >>> >> <mih...@google.com> >> >>> >> wrote: >> >>> >> > Is it all POST requests that fail, or just those to edit-tag?
>> >>> >> > Mihai
>> >>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi >> >>> >> > <jayeshsa...@gmail.com> >> >>> >> > wrote:
>> >>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi >> >>> >> >> <jayeshsa...@gmail.com> >> >>> >> >> wrote: >> >>> >> >> > Hi Brad,
>> >>> >> >> > I think I have tested all the endpoints so far and except for >> >>> >> >> > the >> >>> >> >> > two >> >>> >> >> > all others are working.
>> >>> >> >> > The failing ones are edit-tags and subscriptions/export.
>> >>> >> >> > Please let me know if you find something wrong about these end >> >>> >> >> > points >> >>> >> >> > on google reader side. >> >>> >> >> > -- >> >>> >> >> > Jayesh
>> >>> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi >> >>> >> >> > <jayeshsa...@gmail.com> >> >>> >> >> > wrote: >> >>> >> >> >> Hi Brad, >> >>> >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized >> >>> >> >> >> with >> >>> >> >> >> OAuth.
>> >>> >> >> >> Are you sure you have enabled OAuth on edit-tag requests? >> >>> >> >> >> Thanks. >> >>> >> >> >> -- >> >>> >> >> >> Jayesh
>> >>> >> >> >> On Sat, Mar 27, 2010 at 10:53 PM, Jayesh Salvi >> >>> >> >> >> <jayeshsa...@gmail.com> >> >>> >> >> >> wrote:
>> >>> >> >> >>>> Do I need to expand the "scope" while asking for OAuth >> >>> >> >> >>>> tokens? >> >>> >> >> >>>> if >> >>> >> >> >>>> it's possible that is.
>> >>> >> >> >>> This indeed did the trick. I changed scope to:
>> >>> >> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes >> >>> >> >> >>>> <bhaw...@google.com> >> >>> >> >> >>>> wrote:
>> >>> >> >> >>>>> I have enabled OAuth on the subscription export so you >> >>> >> >> >>>>> should >> >>> >> >> >>>>> be >> >>> >> >> >>>>> able to use that as well now. >> >>> >> >> >>>>> I can't say definitively what Google is going to do with >> >>> >> >> >>>>> respect >> >>> >> >> >>>>> to >> >>> >> >> >>>>> auth systems, however OAuth is not experimental, I fully >> >>> >> >> >>>>> expect >> >>> >> >> >>>>> its support >> >>> >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to >> >>> >> >> >>>>> ClientLogin >> >>> >> >> >>>>> now so that >> >>> >> >> >>>>> users don't have to provide Google credentials to third >> >>> >> >> >>>>> party >> >>> >> >> >>>>> applications. >> >>> >> >> >>>>> -Brad >> >>> >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi >> >>> >> >> >>>>> <jayeshsa...@gmail.com> wrote:
>> >>> >> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least >> >>> >> >> >>>>>> for >> >>> >> >> >>>>>> subscription list). >> >>> >> >> >>>>>> Here is example code: >> >>> >> >> >>>>>> http://pastebin.com/VbusAELq >> >>> >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run >> >>> >> >> >>>>>> from >> >>> >> >> >>>>>> desktop, but can be used for Android with some >> >>> >> >> >>>>>> modifications. >> >>> >> >> >>>>>> I am yet to test all calls to make sure they work with >> >>> >> >> >>>>>> OAuth, >> >>> >> >> >>>>>> but >> >>> >> >> >>>>>> this is a good start. >> >>> >> >> >>>>>> Brad, could you enable OAuth on subscriptions/export >> >>> >> >> >>>>>> request? >> >>> >> >> >>>>>> My >> >>> >> >> >>>>>> android app (ReaderScope) uses it to download OPML data. >> >>> >> >> >>>>>> Also, one question to Google Reader team. Is the OAuth >> >>> >> >> >>>>>> support >> >>> >> >> >>>>>> an >> >>> >> >> >>>>>> experiment or can I start using it in real world and >> >>> >> >> >>>>>> deploy >> >>> >> >> >>>>>> it >> >>> >> >> >>>>>> in my app? (I >> >>> >> >> >>>>>> know GReader API is not official, but I just want to make >> >>> >> >> >>>>>> sure >> >>> >> >> >>>>>> that OAuth >> >>> >> >> >>>>>> won't go away all of a sudden) >> >>> >> >> >>>>>> Thanks again for the OAuth support. >> >>> >> >> >>>>>> -- >> >>> >> >> >>>>>> Jayesh
I got most of the calls working (including some POST queries) with apache http library and SignPost. But I am still getting error with OPML query. It's a simple GET query on www.google.com/reader/subscriptions/export, but it fails with 401 Client error and I get following warning somewhere inside the http/signpost library:
On Fri, Apr 2, 2010 at 7:48 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > -- > Jayesh
> On Fri, Apr 2, 2010 at 1:58 AM, Brad Hawkes <bhaw...@google.com> wrote: >> Hi Jayesh, >> I looked up your request and it was indeed an error due to an invalid >> signature. >> I think the problem you are having is a known issue with SignPost. >> From http://code.google.com/p/oauth-signpost/wiki/GettingStarted : >> When using HttpURLConnection, you cannot sign POST requests that carry query >> parameters in the message payload (i.e. requests of type >> application/x-www-form-urlencoded). This is not a limitation of Signpost per >> se, but with the way URLConnection works. Server communication with >> URLConnection is based on data streams, which means that whenever you write >> something to the connection, it will be sent to the server immediately. This >> data is not buffered, and there is simply no way for Signpost to inspect >> that data and include it in a signature. Hence, when you have to sign >> requests which contain parameters in their body, you have to use an HTTP >> library like Apache Commons HttpComponents and the respective Signpost >> module. (This restriction does not apply to requests which send binary data >> such as documents or files, because that data won't become part of the >> signature anyway.) >> -Brad
> Thanks a bunch Brad. That seems to explain it. I will try the > suggestions later today and report what I find.
>> On Thu, Apr 1, 2010 at 11:52 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>> Hi guys,
>>> I tried all I could think of, but no help.
>>> I analysed the java SignPost library I was using and dumped the post >>> params/ signature base string etc. But couldn't find anything useful.
>>> I also tried couple of python libraries to get more sample points, but >>> couldn't get those libraries beyond getRequestToken. They all are well >>> tested for Twitter, but can't seem to handle the "scope" post param >>> required for Google oauth.
>>> IIRC, you guys can lookup the requests in server logs based on User >>> Agent strings. Do you think you can tell me if you find something >>> there? I ran the test that marks an item read about 5-10 min ago, with >>> the SOURCE http header set to "ReaderScope 1.8.5x". I got >>> 401-Unauthorized for an edit-tag method invocation. Can Google Reader >>> log tell what in particular went wrong in that request? There should >>> be only one request with that SOURCE field, so it should be easily >>> searchable provided it is kept in logs.
>>> It's difficult at the client side, because there are many things that >>> can go wrong in signing the OAuth request properly. It doesn't help >>> that server returns same error code for all of those errors (401).
>>> Let me know if you can help or have any more suggestions.
>>> Thanks. >>> -- >>> Jayesh
>>> On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com> >>> wrote: >>> > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> >>> > wrote: >>> >> Jayesh, >>> >> OAuth is supported by our authentication library natively. I just >>> >> enabled it >>> >> on the various paths mentioned including edit-tag .
>>> > Could you tell me which client library did you use to test (if it is >>> > publicly available)? I can recheck my code against it. >>> > I am using SignPost, which apparently seems to be a standard OAuth >>> > library, but I will check.
>>> >> It would probably be >>> >> good to verify that you are correctly encoding the POST variables into >>> >> the >>> >> OAuth base signature string. >>> >> -Brad >>> >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> >>> >> wrote:
>>> >>> -- >>> >>> Jayesh
>>> >>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> >>> >>> wrote: >>> >>> > Are you providing the T action token? That's still required even >>> >>> > with >>> >>> > OAuth.
>>> >>> Yes I am doing that. My code is unchanged except for OAuth signing at >>> >>> lower level, so I am adding POST params just like before, including >>> >>> the Token.
>>> >>> > Mihai
>>> >>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi >>> >>> > <jayeshsa...@gmail.com> >>> >>> > wrote:
>>> >>> >> I checked again. It seems it IS failing for many POST requests, >>> >>> >> except >>> >>> >> for >>> >>> >> one.
>>> >>> >> The POST requests to "api/0/stream/items/contents" are successful.
>>> >>> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", >>> >>> >> "api/0/edit-tag" fail. >>> >>> >> -- >>> >>> >> Jayesh
>>> >>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita >>> >>> >> <mih...@google.com> >>> >>> >> wrote: >>> >>> >> > Is it all POST requests that fail, or just those to edit-tag?
>>> >>> >> > Mihai
>>> >>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi >>> >>> >> > <jayeshsa...@gmail.com> >>> >>> >> > wrote:
>>> >>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi >>> >>> >> >> <jayeshsa...@gmail.com> >>> >>> >> >> wrote: >>> >>> >> >> > Hi Brad,
>>> >>> >> >> > I think I have tested all the endpoints so far and except for >>> >>> >> >> > the >>> >>> >> >> > two >>> >>> >> >> > all others are working.
>>> >>> >> >> > The failing ones are edit-tags and subscriptions/export.
>>> >>> >> >> > Please let me know if you find something wrong about these end >>> >>> >> >> > points >>> >>> >> >> > on google reader side. >>> >>> >> >> > -- >>> >>> >> >> > Jayesh
>>> >>> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi >>> >>> >> >> > <jayeshsa...@gmail.com> >>> >>> >> >> > wrote: >>> >>> >> >> >> Hi Brad, >>> >>> >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized >>> >>> >> >> >> with >>> >>> >> >> >> OAuth.
>>> >>> >> >> >> Are you sure you have enabled OAuth on edit-tag requests? >>> >>> >> >> >> Thanks. >>> >>> >> >> >> -- >>> >>> >> >> >> Jayesh
>>> >>> >> >> >> On Sat, Mar 27, 2010 at 10:53 PM, Jayesh Salvi >>> >>> >> >> >> <jayeshsa...@gmail.com> >>> >>> >> >> >> wrote:
>>> >>> >> >> >>>> Do I need to expand the "scope" while asking for OAuth >>> >>> >> >> >>>> tokens? >>> >>> >> >> >>>> if >>> >>> >> >> >>>> it's possible that is.
>>> >>> >> >> >>> This indeed did the trick. I changed scope to:
>>> >>> >> >> >>>> On Fri, Mar 26, 2010 at 12:21 AM, Brad Hawkes >>> >>> >> >> >>>> <bhaw...@google.com> >>> >>> >> >> >>>> wrote:
>>> >>> >> >> >>>>> I have enabled OAuth on the subscription export so you >>> >>> >> >> >>>>> should >>> >>> >> >> >>>>> be >>> >>> >> >> >>>>> able to use that as well now. >>> >>> >> >> >>>>> I can't say definitively what Google is going to do with >>> >>> >> >> >>>>> respect >>> >>> >> >> >>>>> to >>> >>> >> >> >>>>> auth systems, however OAuth is not experimental, I fully >>> >>> >> >> >>>>> expect >>> >>> >> >> >>>>> its support >>> >>> >> >> >>>>> to outlast ClientLogin. We actually prefer OAuth to >>> >>> >> >> >>>>> ClientLogin >>> >>> >> >> >>>>> now so that >>> >>> >> >> >>>>> users don't have to provide Google credentials to third >>> >>> >> >> >>>>> party >>> >>> >> >> >>>>> applications. >>> >>> >> >> >>>>> -Brad >>> >>> >> >> >>>>> On Tue, Mar 23, 2010 at 9:37 PM, Jayesh Salvi >>> >>> >> >> >>>>> <jayeshsa...@gmail.com> wrote:
>>> >>> >> >> >>>>>> Ok, I got the OAuth working with Google Reader (at least >>> >>> >> >> >>>>>> for >>> >>> >> >> >>>>>> subscription list). >>> >>> >> >> >>>>>> Here is example code: >>> >>> >> >> >>>>>> http://pastebin.com/VbusAELq >>> >>> >> >> >>>>>> It uses SignPost for OAuth. It's generic java code run
Now I am making other GET requests which are returning success. So I dumped their request headers and verified that they look the same as the above request.
As I understand it from the RFC, the server is challenging the client to provide OAuth credentials. But as you see, I am providing them in the request. So my best guess on this is that even though OAuth might be enabled on subscriptions/export, it does not fall into the same space as other requests. That is why it is in a way prompting the client to do OAuth authentication by suggesting the OAuthGetRequestToken URL (first step in OAuth authentication process).
On Sat, Apr 3, 2010 at 11:57 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: > I got most of the calls working (including some POST queries) with > apache http library and SignPost. But I am still getting error with > OPML query. It's a simple GET query on > www.google.com/reader/subscriptions/export, but it fails with 401 > Client error and I get following warning somewhere inside the > http/signpost library:
> On Fri, Apr 2, 2010 at 7:48 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote: >> -- >> Jayesh
>> On Fri, Apr 2, 2010 at 1:58 AM, Brad Hawkes <bhaw...@google.com> wrote: >>> Hi Jayesh, >>> I looked up your request and it was indeed an error due to an invalid >>> signature. >>> I think the problem you are having is a known issue with SignPost. >>> From http://code.google.com/p/oauth-signpost/wiki/GettingStarted : >>> When using HttpURLConnection, you cannot sign POST requests that carry query >>> parameters in the message payload (i.e. requests of type >>> application/x-www-form-urlencoded). This is not a limitation of Signpost per >>> se, but with the way URLConnection works. Server communication with >>> URLConnection is based on data streams, which means that whenever you write >>> something to the connection, it will be sent to the server immediately. This >>> data is not buffered, and there is simply no way for Signpost to inspect >>> that data and include it in a signature. Hence, when you have to sign >>> requests which contain parameters in their body, you have to use an HTTP >>> library like Apache Commons HttpComponents and the respective Signpost >>> module. (This restriction does not apply to requests which send binary data >>> such as documents or files, because that data won't become part of the >>> signature anyway.) >>> -Brad
>> Thanks a bunch Brad. That seems to explain it. I will try the >> suggestions later today and report what I find.
>>> On Thu, Apr 1, 2010 at 11:52 AM, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
>>>> Hi guys,
>>>> I tried all I could think of, but no help.
>>>> I analysed the java SignPost library I was using and dumped the post >>>> params/ signature base string etc. But couldn't find anything useful.
>>>> I also tried couple of python libraries to get more sample points, but >>>> couldn't get those libraries beyond getRequestToken. They all are well >>>> tested for Twitter, but can't seem to handle the "scope" post param >>>> required for Google oauth.
>>>> IIRC, you guys can lookup the requests in server logs based on User >>>> Agent strings. Do you think you can tell me if you find something >>>> there? I ran the test that marks an item read about 5-10 min ago, with >>>> the SOURCE http header set to "ReaderScope 1.8.5x". I got >>>> 401-Unauthorized for an edit-tag method invocation. Can Google Reader >>>> log tell what in particular went wrong in that request? There should >>>> be only one request with that SOURCE field, so it should be easily >>>> searchable provided it is kept in logs.
>>>> It's difficult at the client side, because there are many things that >>>> can go wrong in signing the OAuth request properly. It doesn't help >>>> that server returns same error code for all of those errors (401).
>>>> Let me know if you can help or have any more suggestions.
>>>> Thanks. >>>> -- >>>> Jayesh
>>>> On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com> >>>> wrote: >>>> > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> >>>> > wrote: >>>> >> Jayesh, >>>> >> OAuth is supported by our authentication library natively. I just >>>> >> enabled it >>>> >> on the various paths mentioned including edit-tag .
>>>> > Could you tell me which client library did you use to test (if it is >>>> > publicly available)? I can recheck my code against it. >>>> > I am using SignPost, which apparently seems to be a standard OAuth >>>> > library, but I will check.
>>>> >> It would probably be >>>> >> good to verify that you are correctly encoding the POST variables into >>>> >> the >>>> >> OAuth base signature string. >>>> >> -Brad >>>> >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <jayeshsa...@gmail.com> >>>> >> wrote:
>>>> >>> -- >>>> >>> Jayesh
>>>> >>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <mih...@google.com> >>>> >>> wrote: >>>> >>> > Are you providing the T action token? That's still required even >>>> >>> > with >>>> >>> > OAuth.
>>>> >>> Yes I am doing that. My code is unchanged except for OAuth signing at >>>> >>> lower level, so I am adding POST params just like before, including >>>> >>> the Token.
>>>> >>> > Mihai
>>>> >>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi >>>> >>> > <jayeshsa...@gmail.com> >>>> >>> > wrote:
>>>> >>> >> I checked again. It seems it IS failing for many POST requests, >>>> >>> >> except >>>> >>> >> for >>>> >>> >> one.
>>>> >>> >> The POST requests to "api/0/stream/items/contents" are successful.
>>>> >>> >> But POST requests to "api/0/item/edit", "api/0/mark-all-as-read", >>>> >>> >> "api/0/edit-tag" fail. >>>> >>> >> -- >>>> >>> >> Jayesh
>>>> >>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita >>>> >>> >> <mih...@google.com> >>>> >>> >> wrote: >>>> >>> >> > Is it all POST requests that fail, or just those to edit-tag?
>>>> >>> >> > Mihai
>>>> >>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi >>>> >>> >> > <jayeshsa...@gmail.com> >>>> >>> >> > wrote:
>>>> >>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi >>>> >>> >> >> <jayeshsa...@gmail.com> >>>> >>> >> >> wrote: >>>> >>> >> >> > Hi Brad,
>>>> >>> >> >> > I think I have tested all the endpoints so far and except for >>>> >>> >> >> > the >>>> >>> >> >> > two >>>> >>> >> >> > all others are working.
>>>> >>> >> >> > The failing ones are edit-tags and subscriptions/export.
>>>> >>> >> >> > Please let me know if you find something wrong about these end >>>> >>> >> >> > points >>>> >>> >> >> > on google reader side. >>>> >>> >> >> > -- >>>> >>> >> >> > Jayesh
>>>> >>> >> >> > On Sun, Mar 28, 2010 at 9:27 AM, Jayesh Salvi >>>> >>> >> >> > <jayeshsa...@gmail.com> >>>> >>> >> >> > wrote: >>>> >>> >> >> >> Hi Brad, >>>> >>> >> >> >> Now I am stuck on edit-tags, it is returning 401 Unauthorized >>>> >>> >> >> >> with >>>> >>> >> >> >> OAuth.
> Now I am making other GET requests which are returning success. So I > dumped their request headers and verified that they look the same as > the above request.
> As I understand it from the RFC, the server is challenging the client > to provide OAuth credentials. But as you see, I am providing them in > the request. So my best guess on this is that even though OAuth might > be enabled on subscriptions/export, it does not fall into the same > space as other requests. That is why it is in a way prompting the > client to do OAuth authentication by suggesting the > OAuthGetRequestToken URL (first step in OAuth authentication process).
> Does this make sense?
> Please let me know. Thanks. > -- > Jayesh
> On Sat, Apr 3, 2010 at 11:57 AM, Jayesh Salvi <jayeshsa...@gmail.com> > wrote: > > I got most of the calls working (including some POST queries) with > > apache http library and SignPost. But I am still getting error with > > OPML query. It's a simple GET query on > > www.google.com/reader/subscriptions/export, but it fails with 401 > > Client error and I get following warning somewhere inside the > > http/signpost library:
> >> On Fri, Apr 2, 2010 at 1:58 AM, Brad Hawkes <bhaw...@google.com> wrote: > >>> Hi Jayesh, > >>> I looked up your request and it was indeed an error due to an invalid > >>> signature. > >>> I think the problem you are having is a known issue with SignPost. > >>> From http://code.google.com/p/oauth-signpost/wiki/GettingStarted : > >>> When using HttpURLConnection, you cannot sign POST requests that carry > query > >>> parameters in the message payload (i.e. requests of type > >>> application/x-www-form-urlencoded). This is not a limitation of > Signpost per > >>> se, but with the way URLConnection works. Server communication with > >>> URLConnection is based on data streams, which means that whenever you > write > >>> something to the connection, it will be sent to the server immediately. > This > >>> data is not buffered, and there is simply no way for Signpost to > inspect > >>> that data and include it in a signature. Hence, when you have to sign > >>> requests which contain parameters in their body, you have to use an > HTTP > >>> library like Apache Commons HttpComponents and the respective Signpost > >>> module. (This restriction does not apply to requests which send binary > data > >>> such as documents or files, because that data won't become part of the > >>> signature anyway.) > >>> -Brad
> >> Thanks a bunch Brad. That seems to explain it. I will try the > >> suggestions later today and report what I find.
> >>> On Thu, Apr 1, 2010 at 11:52 AM, Jayesh Salvi <jayeshsa...@gmail.com> > wrote:
> >>>> Hi guys,
> >>>> I tried all I could think of, but no help.
> >>>> I analysed the java SignPost library I was using and dumped the post > >>>> params/ signature base string etc. But couldn't find anything useful.
> >>>> I also tried couple of python libraries to get more sample points, but > >>>> couldn't get those libraries beyond getRequestToken. They all are well > >>>> tested for Twitter, but can't seem to handle the "scope" post param > >>>> required for Google oauth.
> >>>> IIRC, you guys can lookup the requests in server logs based on User > >>>> Agent strings. Do you think you can tell me if you find something > >>>> there? I ran the test that marks an item read about 5-10 min ago, with > >>>> the SOURCE http header set to "ReaderScope 1.8.5x". I got > >>>> 401-Unauthorized for an edit-tag method invocation. Can Google Reader > >>>> log tell what in particular went wrong in that request? There should > >>>> be only one request with that SOURCE field, so it should be easily > >>>> searchable provided it is kept in logs.
> >>>> It's difficult at the client side, because there are many things that > >>>> can go wrong in signing the OAuth request properly. It doesn't help > >>>> that server returns same error code for all of those errors (401).
> >>>> Let me know if you can help or have any more suggestions.
> >>>> Thanks. > >>>> -- > >>>> Jayesh
> >>>> On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com> > >>>> wrote: > >>>> > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com> > >>>> > wrote: > >>>> >> Jayesh, > >>>> >> OAuth is supported by our authentication library natively. I just > >>>> >> enabled it > >>>> >> on the various paths mentioned including edit-tag .
> >>>> > Could you tell me which client library did you use to test (if it is > >>>> > publicly available)? I can recheck my code against it. > >>>> > I am using SignPost, which apparently seems to be a standard OAuth > >>>> > library, but I will check.
> >>>> >> It would probably be > >>>> >> good to verify that you are correctly encoding the POST variables > into > >>>> >> the > >>>> >> OAuth base signature string. > >>>> >> -Brad > >>>> >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi < > jayeshsa...@gmail.com> > >>>> >> wrote:
> >>>> >>> -- > >>>> >>> Jayesh
> >>>> >>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita < > mih...@google.com> > >>>> >>> wrote: > >>>> >>> > Are you providing the T action token? That's still required even > >>>> >>> > with > >>>> >>> > OAuth.
> >>>> >>> Yes I am doing that. My code is unchanged except for OAuth signing > at > >>>> >>> lower level, so I am adding POST params just like before, > including > >>>> >>> the Token.
> >>>> >>> > Mihai
> >>>> >>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi > >>>> >>> > <jayeshsa...@gmail.com> > >>>> >>> > wrote:
> >>>> >>> >> I checked again. It seems it IS failing for many POST requests, > >>>> >>> >> except > >>>> >>> >> for > >>>> >>> >> one.
> >>>> >>> >> The POST requests to "api/0/stream/items/contents" are > successful.
> >>>> >>> >> But POST requests to "api/0/item/edit", > "api/0/mark-all-as-read", > >>>> >>> >> "api/0/edit-tag" fail. > >>>> >>> >> -- > >>>> >>> >> Jayesh
> >>>> >>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita > >>>> >>> >> <mih...@google.com> > >>>> >>> >> wrote: > >>>> >>> >> > Is it all POST requests that fail, or just those to edit-tag?
> >>>> >>> >> > Mihai
> >>>> >>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi > >>>> >>> >> > <jayeshsa...@gmail.com> > >>>> >>> >> > wrote:
> >>>> >>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi > >>>> >>> >> >> <jayeshsa...@gmail.com> > >>>> >>> >> >> wrote: > >>>> >>> >> >> > Hi Brad,
> >>>> >>> >> >> > I think I have tested all the endpoints so far and except > for > >>>> >>> >> >> > the > >>>> >>> >> >> > two > >>>> >>> >> >> > all others are working.
> >>>> >>> >> >> > The failing ones are edit-tags and subscriptions/export.
> > Now I am making other GET requests which are returning success. So I
> > dumped their request headers and verified that they look the same as
> > the above request.
> > I looked into the following RFC about the 401 response generated by
> > the server and the meaning of "WWW-authenticate: OAuth realm"
> >http://tools.ietf.org/html/rfc2617#section-1.2
> > As I understand it from the RFC, the server is challenging the client
> > to provide OAuth credentials. But as you see, I am providing them in
> > the request. So my best guess on this is that even though OAuth might
> > be enabled on subscriptions/export, it does not fall into the same
> > space as other requests. That is why it is in a way prompting the
> > client to do OAuth authentication by suggesting the
> > OAuthGetRequestToken URL (first step in OAuth authentication process).
> > Does this make sense?
> > Please let me know. Thanks.
> > --
> > Jayesh
> > On Sat, Apr 3, 2010 at 11:57 AM, Jayesh Salvi <jayeshsa...@gmail.com>
> > wrote:
> > > I got most of the calls working (including some POST queries) with
> > > apache http library and SignPost. But I am still getting error with
> > > OPML query. It's a simple GET query on
> > >www.google.com/reader/subscriptions/export, but it fails with 401
> > > Client error and I get following warning somewhere inside the
> > > http/signpost library:
> > >> On Fri, Apr 2, 2010 at 1:58 AM, Brad Hawkes <bhaw...@google.com> wrote:
> > >>> Hi Jayesh,
> > >>> I looked up your request and it was indeed an error due to an invalid
> > >>> signature.
> > >>> I think the problem you are having is a known issue with SignPost.
> > >>> Fromhttp://code.google.com/p/oauth-signpost/wiki/GettingStarted: > > >>> When using HttpURLConnection, you cannot sign POST requests that carry
> > query
> > >>> parameters in the message payload (i.e. requests of type
> > >>> application/x-www-form-urlencoded). This is not a limitation of
> > Signpost per
> > >>> se, but with the way URLConnection works. Server communication with
> > >>> URLConnection is based on data streams, which means that whenever you
> > write
> > >>> something to the connection, it will be sent to the server immediately.
> > This
> > >>> data is not buffered, and there is simply no way for Signpost to
> > inspect
> > >>> that data and include it in a signature. Hence, when you have to sign
> > >>> requests which contain parameters in their body, you have to use an
> > HTTP
> > >>> library like Apache Commons HttpComponents and the respective Signpost
> > >>> module. (This restriction does not apply to requests which send binary
> > data
> > >>> such as documents or files, because that data won't become part of the
> > >>> signature anyway.)
> > >>> -Brad
> > >> Thanks a bunch Brad. That seems to explain it. I will try the
> > >> suggestions later today and report what I find.
> > >>> On Thu, Apr 1, 2010 at 11:52 AM, Jayesh Salvi <jayeshsa...@gmail.com>
> > wrote:
> > >>>> Hi guys,
> > >>>> I tried all I could think of, but no help.
> > >>>> I analysed the java SignPost library I was using and dumped the post
> > >>>> params/ signature base string etc. But couldn't find anything useful.
> > >>>> I also tried couple of python libraries to get more sample points, but
> > >>>> couldn't get those libraries beyond getRequestToken. They all are well
> > >>>> tested for Twitter, but can't seem to handle the "scope" post param
> > >>>> required for Google oauth.
> > >>>> IIRC, you guys can lookup the requests in server logs based on User
> > >>>> Agent strings. Do you think you can tell me if you find something
> > >>>> there? I ran the test that marks an item read about 5-10 min ago, with
> > >>>> the SOURCE http header set to "ReaderScope 1.8.5x". I got
> > >>>> 401-Unauthorized for an edit-tag method invocation. Can Google Reader
> > >>>> log tell what in particular went wrong in that request? There should
> > >>>> be only one request with that SOURCE field, so it should be easily
> > >>>> searchable provided it is kept in logs.
> > >>>> It's difficult at the client side, because there are many things that
> > >>>> can go wrong in signing the OAuth request properly. It doesn't help
> > >>>> that server returns same error code for all of those errors (401).
> > >>>> Let me know if you can help or have any more suggestions.
> > >>>> Thanks.
> > >>>> --
> > >>>> Jayesh
> > >>>> On Thu, Apr 1, 2010 at 12:04 AM, Jayesh Salvi <jayeshsa...@gmail.com>
> > >>>> wrote:
> > >>>> > On Wed, Mar 31, 2010 at 11:20 PM, Brad Hawkes <bhaw...@google.com>
> > >>>> > wrote:
> > >>>> >> Jayesh,
> > >>>> >> OAuth is supported by our authentication library natively. I just
> > >>>> >> enabled it
> > >>>> >> on the various paths mentioned including edit-tag .
> > >>>> > Could you tell me which client library did you use to test (if it is
> > >>>> > publicly available)? I can recheck my code against it.
> > >>>> > I am using SignPost, which apparently seems to be a standard OAuth
> > >>>> > library, but I will check.
> > >>>> >> It would probably be
> > >>>> >> good to verify that you are correctly encoding the POST variables
> > into
> > >>>> >> the
> > >>>> >> OAuth base signature string.
> > >>>> >> -Brad
> > >>>> >> On Tue, Mar 30, 2010 at 8:02 PM, Jayesh Salvi <
> > jayeshsa...@gmail.com>
> > >>>> >> wrote:
> > >>>> >>> --
> > >>>> >>> Jayesh
> > >>>> >>> On Wed, Mar 31, 2010 at 8:29 AM, Mihai Parparita <
> > mih...@google.com>
> > >>>> >>> wrote:
> > >>>> >>> > Are you providing the T action token? That's still required even
> > >>>> >>> > with
> > >>>> >>> > OAuth.
> > >>>> >>> Yes I am doing that. My code is unchanged except for OAuth signing
> > at
> > >>>> >>> lower level, so I am adding POST params just like before,
> > including
> > >>>> >>> the Token.
> > >>>> >>> > Mihai
> > >>>> >>> > On Tue, Mar 30, 2010 at 10:57 PM, Jayesh Salvi
> > >>>> >>> > <jayeshsa...@gmail.com>
> > >>>> >>> > wrote:
> > >>>> >>> >> I checked again. It seems it IS failing for many POST requests,
> > >>>> >>> >> except
> > >>>> >>> >> for
> > >>>> >>> >> one.
> > >>>> >>> >> The POST requests to "api/0/stream/items/contents" are
> > successful.
> > >>>> >>> >> On Wed, Mar 31, 2010 at 8:12 AM, Mihai Parparita
> > >>>> >>> >> <mih...@google.com>
> > >>>> >>> >> wrote:
> > >>>> >>> >> > Is it all POST requests that fail, or just those to edit-tag?
> > >>>> >>> >> > Mihai
> > >>>> >>> >> > On Tue, Mar 30, 2010 at 9:47 PM, Jayesh Salvi
> > >>>> >>> >> > <jayeshsa...@gmail.com>
> > >>>> >>> >> > wrote:
> > >>>> >>> >> >> On Tue, Mar 30, 2010 at 12:18 AM, Jayesh Salvi
> > >>>> >>> >> >> <jayeshsa...@gmail.com>
> > >>>> >>> >> >> wrote:
> > >>>> >>> >> >> > Hi Brad,
> > >>>> >>> >> >> > I think I have tested all the endpoints so far and except
> > for
> > >>>> >>> >> >> > the
> > >>>> >>> >> >> > two
> > >>>> >>> >> >> > all others are working.
> > >>>> >>> >> >> > The failing ones are edit-tags and subscriptions/export.
