Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

assuming you're talking about first-party clients connecting to your API, you still likely just want kratos. hydra (i.e. oauth) is for third-party access to your APIs - <https://www.ory.sh/oauth2-openid-connect-do-you-need-use-cases-examples/>

Thanks <@U02AY3MNVKP> so I have to go with the cookie session way, right?

It likely depends on what client is calling the API. If it's from a browser, a cookie session is probably the most straightforward.

I would also recommend looking into Oathkeeper to function as a proxy to handle the client auth, allowing you to mutate different client authentication mechanisms into a single internal form like their id_token mutator, then your API only needs to interpret the id_token from Oathkeeper and Oathkeeper can be responsible for all possible client approaches

we'll have both clients using browsers and clients using SDKs from different P languages. But that sounds good. I'll take a look at the Oathkeeper docs then. Thank you!