Hello,

At the office, we're working on an application and ArcadeDB is the only database we want to rely on.

As we need a JWT token, we decided to use the ArcadeDB user system instead of using LDAP or ActiveDirectory.

Login and registration endpoints works correctly as it execute user registration using root account and login using user provided creditentials.

Issue is that, after being connected, the client will execute a query on endpoint /do_something JWT token will report user as being user "Ben" but as it need to executes queries in it's name (Because if the database visibility/rights system is in place in arcadeDB, no need to re-code it on our side) we need to send a query using the user password.

And this is where we're stuck, we CANNOT (should not, actually) store the user password in the JWT temporary database.

However, if ArcadeDB was returning a token for authentification, we could with no much worry store this temporary token in the JWT database and the user password would be safe.

TL;DR :

In our application user system is literally using ArcadeDB user's accounts system, which means that for each action on the database that is executed by the application need to be done in the user's name, which requires the username/password to be saved after login, during the whole token time of life.

Adding a token system for authentification would help a lot.

We only use the HTTP/REST API.

Thanks.