-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/13/09 9:05 PM, Jason Eacott wrote: > Hi All,
Howdy. :) > I've been trying to understand oauth for xmpp and have a couple of > questions, I hope someone can answer :) > > I'm a bit confused as to what exactly the producer consists of. > For example, should an xmpp server accept the oauth stanza and > subsequently forward the given request as the oauth alias? > clear as mud I know, but I'm asking if I send a message containing > the details: > from=somejidA > to=somejidB > oauth alias=somejidC > > then should/could an xmpp server rewrite this as simply: > from=somejidC > to=somejidB > > if this isnt the way its supposed to work, then is it up to each > component/client to implement its own oauth impl for every incoming stanza? > sorry if the question seems dumb but I'm still unclear on how to code a > component that reacts to a given subelement (ie oauth) > and apply its outcome to the wrapping element. > > I hope someone can make my head less murky ;-) Hmm. :) First, what exactly are you trying to accomplish? Perhaps you could describe your use case a bit more. The idea behind XEP-0235 (OAuth Over XMPP) is that the XMPP server isn't really involved, and certainly not involved in rewriting stanzas. Instead, an XMPP client would provide an access token when seeking to do something like publish to a pubsub node or join a chatroom. The client would not obtain the access token over XMPP and similarly the request token would not be obtained over XMPP. Right now all we have defined is a way to include an access token with a particular XMPP request. I hope that clarifies things a bit more. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrZJ6YACgkQNL8k5A2w/vy/4QCfYnQ6Cxw9BjEMXN86gfAhqIYR IvwAoJifIxw4iYYd2qNe9t3AN910Wcld =HbPQ -----END PGP SIGNATURE-----
