I have a couple of questions. We are considering trying to write a
desktop client as a counterpart to our web-based OAuth system. The two
main issues are vetting of clients (so creating unique shared secrets
for each desktop client). is there a better way to do this? The next
issue has to do with clients that cannot get callbacks due to firewall
considerations. Is it possible to still have this be OAuth in this case?
Are there other practical workarounds people have used?
Will OAuth 2 address either of these? We are committed to using OAuth
1.0a for the near term, until there is a reference implementation for
OAuth 2. Any timeline on that?
Thanks in Advance!
Jeff
--
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.
