Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 25 02:00
    gbrlsnchs closed #50
  • Jul 25 02:00
    gbrlsnchs commented #50
  • Jul 25 01:59

    gbrlsnchs on v3.0.1

    (compare)

  • Jul 25 01:56

    gbrlsnchs on master

    Fix "alg" claim for Ed25519 Re… Test against latest versions of… (compare)

  • Jul 25 01:53

    gbrlsnchs on master

    Test against latest versions of… (compare)

  • Jul 25 01:51

    gbrlsnchs on master

    Fix "alg" claim for Ed25519 Re… (compare)

  • Jul 25 01:44
    gbrlsnchs labeled #50
  • Jul 25 01:41
    gbrlsnchs unlabeled #50
  • Jul 25 01:41
    gbrlsnchs labeled #50
  • Jul 23 17:17
    gbrlsnchs closed #51
  • Jul 23 17:17
    gbrlsnchs commented #51
  • Jul 23 04:37
    noecs labeled #51
  • Jul 23 04:37
    noecs assigned #51
  • Jul 23 04:37
    noecs opened #51
  • Jul 10 10:54
    Mark90 commented #48
  • Jun 05 22:28
    rorycl edited #50
  • Jun 05 22:26
    rorycl opened #50
  • Jun 05 22:26
    rorycl labeled #50
  • Jun 05 22:26
    rorycl assigned #50
  • Apr 04 23:45
    gbrlsnchs commented #49
Aditya Sadawarte
@addy419
I'm new to go, and working on my website.
Is this library production ready?
Like node/jsonwebtokens
Gabriel Sanches
@gbrlsnchs
hey @addy419, sorry for taking some time to answer... yes, it's production ready... v2 only works with go1.10+ and I'm currently working on v3, which will only work with go1.11+
Liam Read
@LiamDotPro
Hey
Im trying to work with this package but for whatever reason I'm not able to get the /v3 working in my project
It has previously worked in the past, I think it might be something to do with modules
Is the documentation for working with JWT's in this package out of date?
Gabriel Sanches
@gbrlsnchs
@LiamDotPro I have answered you in Github. Nonetheless, you should have no issues with this library using modules (actually, the current version only supports installing it with modules)
Gustavo Hoirisch
@gugahoi
What is the correctr way to go about parsing custom fields in the token? I find that I can run through Verify however my custom fields are not populated in my struct. As an example I have an ID field with a user id i'd like to get access to once the jwt has been deemed valid.