Need SQL Server Help

[simon7]

As of now my whole app authenticates via a token. In each flow I then do authorisation. So for my api calls I always include a couple of ids (accountId, userId).
I did experiment with sending both a JWT and also a custom encryption method but am not using this right now (decided it was overkill). See this topic as well:

Any ways to handle user authentication outside of Bubble?

I have actually tested out a system like that. I use a lot of external apis in AWS and looked at ways to create unique tokens on the fly to make authentication and authorization easy on the receiving end. It doesn’t fit the use case discussed here, but might be an inspiration for others. In short, wrote a small serverside plugin with crypto (vanilla-node, so no dependancies). The plugin takes whatever string or array I throw at it, and creates a encrypted token with aes-256-ctr. The tokens co…