hanko VS t3-turbo-and-clerk

I get what you are trying to do, but it feels a bit insecure. Why not use an OSS passwordless project like https://github.com/supertokens/supertokens-core/ or https://github.com/teamhanko/hanko

Hanko.io

Hanko- Open-source authentication and user management for the passkey era. Integrated in minutes, for web and mobile apps.

🌟 Support on GitHub Website: https://www.hanko.io

Link to GitHub -->

You may be able to use Hanko. It offers login and profile components that can freely be styled with CSS. We haven’t tested php integration yet, but it should definitely work.

We’ve built open-source hanko.io for you. Check out the next guide and the example app on GitHub.

You may like Hanko or Hanko Cloud

Thank you for the feedback. We get this question a lot, and it is obviously not ideal right now. Things will get much better with passkey autofill very soon, though.

See also: https://github.com/teamhanko/hanko/discussions/342

In this tutorial, we will implement single sign-on using Clerk, and use GitHub as the OAuth server that'll verify the user’s credentials. We are going to modify an existing application to add protected routes and use the pre-built UI components.

Clerk official example using Nextjs & expo: (no express, webhooks or credential auth) https://github.com/clerk/t3-turbo-and-clerk

I’m currently checking out https://clerk.dev, seems pretty decent so far. The pricing model isn’t ideal but apparently they are redoing it at this moment.

t3-turbo-and-clerk

If you want a complete out of the box easy setup for web and mobile, check this rep out https://github.com/clerkinc/t3-turbo-and-clerk

No I signed up with clerk.dev which made it a lot easier. tbh if it wasn't for them I would have had to hire a developer to help set that up because I had no idea about auth, user databases, and all that.

Some open-source identity solutions I learned could help; integrate with the Logto /Clerk, Ory... API to securely store access tokens that allow Chat GPT to access the user's Logto account; this is a start. But, like these, Security and privacy of service / Technical requirements for integration / User interface for authorization, there’s much to do. It's funny to rethink this topic.

https://clerk.dev meets all of your requirements except ABAC and OSS/self-host. Recommend checking it out if you want something that "just works"

I've def felt your pain before, and it's why I started https://clerk.dev - auth "should just work".