PageRenderTime 33ms CodeModel.GetById 20ms RepoModel.GetById 1ms app.codeStats 0ms

/README

http://github.com/skypher/cl-oauth
#! | 72 lines | 41 code | 31 blank | 0 comment | 0 complexity | 97551c1e29841592b3dac38207632a16 MD5 | raw file
Possible License(s): LGPL-3.0
  1. This is cl-oauth, an implementation of the OAuth 1.0a standard
  2. in Common Lisp.
  3. Spec URI: http://oauth.net/core/1.0a
  4. Section numbers mentioned in the code and documentation
  5. refer to this document, unless mentioned otherwise.
  6. Most of the code has passed basic manual and automated tests,
  7. but the SP code hasn't been used in a real-world application
  8. yet.
  9. Not supported at this time:
  10. Service Provider:
  11. * parameters from Auth header (needs some parsing) [5.4]
  12. in principle a MUST, but as SP you get to decide ;)
  13. * Nonce checking [9], a SHOULD.
  14. * Session extension
  15. http://oauth.googlecode.com/svn/spec/ext/session/1.0/drafts/1/spec.html
  16. * Problem Reporting extension
  17. http://oauth.pbworks.com/ProblemReporting
  18. Consumer:
  19. * Auth parameters should be working, but Google rejects them for
  20. some reason. Do more testing and debugging.
  21. * Revoking tokens as per section 7 of the Session extension
  22. * Problem Reporting extension: fields in body are ignored.
  23. Both:
  24. * crypto signatures different from HMAC-SHA1. It's easy to use
  25. other digests and MACs via Ironclad but RSA needs to have
  26. padding implemented. [9.3]
  27. * PLAINTEXT signature. Meh. [9.4]
  28. * POST and Auth requests are hardly tested yet.
  29. People who contributed in a substantial way to this library:
  30. * Leslie P. Polzer <polzer@port-zero.com>: base implementation.
  31. See also revision log for minor contributions.
  32. TODO (apart from spec things not implemented yet):
  33. * grep the code for TODO and FIXME
  34. * incorporate test cases from http://wiki.oauth.net/TestCases
  35. * abstract token storage, can't get far with volatile memory
  36. FETCH-TOKEN/STORE-TOKEN
  37. * better handling of different protocol versions; in particular
  38. we should support serving both 1.0 and 1.0a clients (and requesting
  39. stuff from 1.0 and 1.0a servers too, of course).
  40. * compare with the Hammer draft spec and resolve differences
  41. * always store the URL-decoded key/secret in the request token