You are here

README.txt in OAuth 1.0 6

Same filename and directory in other branches
  1. 8.2 README.txt
  2. 8 README.txt
A best practices implementation of OAuth for Drupal.  

What is OAuth?

"An open protocol to allow secure API authentication in a simple and
standard method from desktop and web applications."

If you've ever used Flickr to connect with other systems, or added a
Facebook app that asks you what permissions you want to give, both are
examples of securely identifying yourself between systems without you
physically having to enter a password every time.

A very simplistic explanation is that OpenID is like your car key: you
have to be at the web page / service to log in.

OAuth is like a valet key, that you can hand to a website to operate
on your behalf, even when you're not there.

  * Community Site: http://oauth.net/
  * Wikipedia entry: http://en.wikipedia.org/wiki/OAuth
  * Specification: http://oauth.net/core/1.0/
  * Discussion Group: http://groups.google.com/group/oauth
  * PHP Library by Andy Smith (termie): http://code.google.com/p/oauth/

TO DO

1. allow OAuth between two Drupal sites
  a) have the token be passed etc.
  b) some small "thing" that can be done remotely and is non-trivial
  and has few if any dependiences (i.e. core D6 + Oauth on both sides)
  -- probably something with profile.module or username

2. Enable OAuth with some 3rd party system
  a) choose a particular service -- my recommendation is Magnolia --
  http://wiki.ma.gnolia.com/OAuth
  b) implement some small thing -- maybe the beginnings of a magnolia module

File

README.txt
View source
  1. A best practices implementation of OAuth for Drupal.
  2. What is OAuth?
  3. "An open protocol to allow secure API authentication in a simple and
  4. standard method from desktop and web applications."
  5. If you've ever used Flickr to connect with other systems, or added a
  6. Facebook app that asks you what permissions you want to give, both are
  7. examples of securely identifying yourself between systems without you
  8. physically having to enter a password every time.
  9. A very simplistic explanation is that OpenID is like your car key: you
  10. have to be at the web page / service to log in.
  11. OAuth is like a valet key, that you can hand to a website to operate
  12. on your behalf, even when you're not there.
  13. * Community Site: http://oauth.net/
  14. * Wikipedia entry: http://en.wikipedia.org/wiki/OAuth
  15. * Specification: http://oauth.net/core/1.0/
  16. * Discussion Group: http://groups.google.com/group/oauth
  17. * PHP Library by Andy Smith (termie): http://code.google.com/p/oauth/
  18. TO DO
  19. 1. allow OAuth between two Drupal sites
  20. a) have the token be passed etc.
  21. b) some small "thing" that can be done remotely and is non-trivial
  22. and has few if any dependiences (i.e. core D6 + Oauth on both sides)
  23. -- probably something with profile.module or username
  24. 2. Enable OAuth with some 3rd party system
  25. a) choose a particular service -- my recommendation is Magnolia --
  26. http://wiki.ma.gnolia.com/OAuth
  27. b) implement some small thing -- maybe the beginnings of a magnolia module