This message was deleted.
# general
m
This message was deleted.
w
i suppose it depends. are you developing apis that the users will use 1st-party? or are these apis that the users will give access to other applications to use on their behalf under specific restrictions or scopes?
l
my frontend will communicate with the api's. not the user specifically
so, ya only my own apps will communicate with these. But i do need Keto so i know if t he users has permissions to my stuff i'm making
w
then yeah - hydra for oauth2 integration. kratos for user management/identity. your applications would be registered with hydra. you'd configure your users in kratos. also would configure kratos with hydra so your application could initiate consent from the users to your application concerning the api.
not extremely hard but more complicated than some.
l
I figured it might be complicated. :) probably more than this app needs. But I hate seeing all the security issues out there.. So why not just build it right from the start with a nice tool
Instead of fast and insecure