Version 2.0.0

350 views
Skip to first unread message

excpt

unread,
Jun 3, 2015, 4:39:03 AM6/3/15
to ruby...@googlegroups.com
Hi,

my name's Tim (github: excpt) and I'm the ruby-jwt maintainer.

I collected some requested features and planned tasks for the version 2.0 todo-list.

Feature requests:

* Support for encrypted tokens (JWE http://tools.ietf.org/html/rfc7516)
* Better support for plain tokens and specific verification

TODO:

* Drop support for outdated ruby versions 1.8.x and old 1.9.x versions
* Drop echoe dependency for building and publishing the gem
* Code refactoring - drop old functions, update code (e.g. use the more beautifuly hash/symbol syntax)
* Improve tests, clean up code (branch already setup, not all tests ported so far)
* Simplfy usage
* Introduction for code reviews, quality standards, code formatting (e.g. review ninja or code climate, automated tests via travis-ci or codeship, etc.)

Please add your ideas, tasks, features or you name it as a reply. Let's collect the stuff we want/need to implement/improve. :)

Regards,

Tim

ad...@ajmichael.net

unread,
Jul 22, 2015, 3:34:31 PM7/22/15
to ruby-jwt
I think JWE support should be highest priority. At the moment, it seems that we only support 50% of the use cases with JWS.

Is that the purpose of the 2.x branch? Or is that a general purpose refactoring?

excpt

unread,
Jul 22, 2015, 3:50:26 PM7/22/15
to ruby-jwt, ad...@ajmichael.net
That's the purpose of the 2.x branch.

To have a better code base we should split the code into JWE and JWS sections and the algorithms should be implemented in a JWA section.
In the case we have nearly all aspects implemented of the JSON Web Token standard.
Reply all
Reply to author
Forward
0 new messages