Indeed, the draft of Scalable OAuth takes to account the problem of giving access to concrete resources at the Service Provider, as well as other problems I had detected such as token revocation and renewal. Thank you very much to all of you who have tried to help me :-) Jorgito --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
- [oauth] Distinction between Request Token and Acc... Jorgito
- [oauth] Re: Distinction between Request Toke... John Kristian
- [oauth] Re: Distinction between Request Toke... JR Conlin
- [oauth] Re: Distinction between Request ... Jorgito
- [oauth] Re: Distinction between Requ... chris . messina
- [oauth] Re: Distinction between Requ... Krishna Sankar (ksankar)
- [oauth] Re: Distinction between ... Praveen Alavilli
- [oauth] Re: Distinction bet... Jorgito
- [oauth] Re: Distinction between ... Jorgito
- [oauth] Re: Distinction bet... Blaine Cook
- [oauth] Re: Distinction... Jorgito
- [oauth] Re: Distinction... Hans Granqvist
- [oauth] Re: Distinc... Chris Messina
- [oauth] Re: Distinc... Joseph A Holsten
