JWT support for Scala. Bonus extensions for Play, Play JSON, Json4s, Circe, uPickle, Spray and Argonaut
APACHE-2.0 License
Bot releases are hidden (Show)
Published by erwan about 3 years ago
Clock
to Jwt
- before that the system clock was always used. To use your own clock, use Jwt(clock)
instead of just Jwt
(and the equivalent for json libraries).This break binary compatibility (hence the major version) because the signature of the traits and object is no longer the same, however for most users there should be no change required to your source code to compile with this new version.
Published by erwan about 3 years ago
Updated libraries:
All json4s-related artifacts are now published for Scala 3. Additionally, we're using the *-core
dependencies for json4s artifacts. If you were relying on ScalaJWT to bring you the full json4s-native or json4s-jackson you might need to add the dependency explicitely.
Published by erwan over 3 years ago
Published by erwan over 3 years ago
Published by erwan over 3 years ago
Changes
Remarks
Published by erwan over 3 years ago
Published by erwan over 3 years ago
Published by erwan over 3 years ago
Published by erwan over 3 years ago
This release is mostly the same as v7.1.0, except it's published for Scala 3.0.0-RC1 for the libraries that support it.
jwt-core
, jwt-argonaut
and jwt-upickle
are now available for Scala 3.0.0-RC1 in addition to Scala 2.12 and 2.13.Published by erwan over 3 years ago
New features
Published by erwan over 3 years ago
This is a major release because of the typo fix (renaming JwtUnknownAlgorithm
) that breaks binary compatibility.
It shouldn't be an issue for most users as it's mostly used internally, but it's publicly exposed so technically binary compatibility is broken.
JwtUnknownAlgorithm
#182Published by erwan over 3 years ago
Important: the groupId changed from fr.pauldijou
to com.github.jwt-scala
,
so you need to update your dependencies:
libraryDependencies += "com.github.jwt-scala" %% "<artifact>" % "6.0.0"
JwtException
a proper exception (thanks @tpolecat)JwtSession
should always have an expiration now if you have set a play.http.session.maxAge
. Before, a few ways to create the session would forget to add it.refreshJwtSession
on a Play Result will now truly refresh and set a session if there was one to begin with. Before, it would always set a session with an expiration even if there was nothing.Published by pauldijou over 3 years ago
Published by pauldijou almost 5 years ago
signature
is false
on options (thanks @Baccata)Published by pauldijou about 5 years ago
Published by pauldijou about 5 years ago
This is not really a breaking change release but I did some small adjustements that might break in very specific cases so not taking chances.
Jwt
pure Scala implementation around regexp. Again, try not to use this one, mostly for tests and demos.Published by pauldijou over 5 years ago
Published by pauldijou over 5 years ago