Which is also written by us. So you don’t need to worry about it

@tredstone in the new version, it wouldn’t be. However we will implement different measures to ensure misuse like @HyperGo18 mentioned does not happen, or is blocked.

how do we submit feature requests? i think it would be nice to have a hook taht would let you change the jwt payload during a token refresh

Hmm. That’s an interesting feature indeed. You can create an issue about this or implement it yourself and create a pull request 😀

i think i just might, lol

i'm curious to hear some feedback from others on that idea as well

I’ll think about this a bit more and let you know my thoughts!

by the way, are there any plans for a version written in go?

Not yet. We are actually building a version that is slightly better to develop on - right now a problem is that if we want to support 5 frameworks with 5 databases, we have to write a total of 25 repos! And that’s just really difficult to do and maintain. So we are creating a version that has decoupled the framework part from the database part (using a micro service kind of an architecture). If you are currently using the node version, then moving to this new version should not be too much of an issue. And creating go Lang support for this new version will be FAR easier than doing it now.

This new version should be available sometime within the next month

And on that, we will implement the go Lang version for sure. Quite soon

And of course, your welcome to contribute if you need it urgently. Haha

im currently working on a custom port to golang but i can follow the spec and open source it if you'd like

@HyperGo18 as custom port for this library?

ive been integrating it into my custom oauth server written in go

gotcha

or just write the entire library in c/c++ and write language specific wrappers

Yea that’s exactly what our new version is going to be. Except it’s written in Java.

😦

And will have a wrapper for node, go etc etc..

ok

Why that reaction? Haha

java

@rp nice!

Is it cause of Java as opposed to c++?

this should run pretty quick after that. I'd be interested in seeing some benchmark test results comparing the old and the new implementaitons

Yup. That’s in the plan

or compile the java codebase to webassembly 🙂

Why web assembly? That’s a browser specific thing. The Java part is a backend module. Like Cassandra or elasticsearch (which r both also written in Java and scale awesomely)

webassembly outside of the browser is the future of software development