Let hydra work please

U left ur email in the the docs

Shouldn't do that

it is public knowledge

how does hydra work?

are you gonna crack my ssh privat e keys?

Had to kick him unfortunately 😅

hahaha nice

im still chatting with him

he is "hacking" me

Hahah let us know how it goes

i uploaded in reverse order my B

Hi.

Anyone wanna join my security and safety agency? We are new but active

That chat was amazing 😂

Hey @User

Hey guys, I just want to mention that you did a great job on doing such a thing, it is AMAZING.

Hey @User Lord Maximus! Thank you, appreciate your kind words. If you dont mind me asking, why do you think it is amazing?

hey @User

hello everyone, I am exploring authentication architecture for web apps and APIs. Have implemented JWT previously. I am looking to understand more about 1. How to implement server-side logout when using JWT auth mechanism? 2. When do services like supertoken or auth0 make sense to use? What would I have to do on my own if I don't use these services?

1. Without having a blacklist of JWTs on your server, you cannot revoke JWTs before they naturally expire. This is one reason why it is recommended to have short lived JWTs along with long lived refresh tokens (which are not JWTs) 2. In order to build it yourself, you will have to do the following: - Spend weeks and months trying to understand the best security practices. - After understanding them, you will have to spend a few more weeks / months actually building it out (some of the RFCs are 400+ pages long..) - After you have built it, you will have to be responsible for maintaing it for your app - any chanes to the RFCs or browsers (like they added sameSite cookies) or your backend / frontend will probably require a ton of work from your side. - You will also have to take the headache of scaling it as your app grows. - You will have to do all that, plus of course, run your business and app. Any mistakes in session implementation, your app is practically down for all your logged in users. Any security flaws, as your app grows, your user data is likely to be compromised and you may be able to do very little at that point in time. - Instead, you could use a third party library like SuperTokens which does all that for you and has a free version which works for all use cases pertaining to sessions - no matter how many sessions your app will have.

If you want a solution for session management - i.e. user logs into your site and then you want to keep that user logged in for a long time, securely, you should use SuperTokens (I am biased here, of course). If you want a full user management solution and don't mind saving all your user's info in a third party app's servers, you can use Auth0 or Okta or Cognito. But these services do not provide a good session management solution - so you would have to use something like SuperTokens or if you are using node, then express-sessions etc..

@User ^

hey @User !

Hi guys, just saw your twitter post. And I wanted to congratulate you with the backing of the ||secret startup accelerator||. I haven't yet implemented your packages yet but the articles you guys have written about authentication and user session management have been amazing and completely changed my way of thinking and developing these systems. https://twitter.com/supertokensio/status/1255786671645306880

Hi @User,

Thank you so much for your kind wishes and support. We truly appreciate it. We're glad to have helped and will continue to do so

hey @User !

hey

what brings you to our server?