For multiple services, we've been seeing more and more services adopt JWT-based models for SSO. We have a Hasura integration where we'll generate the JWT neces

For multiple services, we've been seeing more and more services adopt JWT-based models for SSO. We have a Hasura integration where we'll generate the JWT necessary for authenticating queries: https://docs.clerk.dev/integrations/hasura https://docs.clerk.dev/integrations/hasura In general, we're pushing for more use of short-lived JWTs to sync identities between trusted parties instead of OAuth. We think this is preferable because it can keep sessions synced, while OAuth tends to result in independent sessions. Admittedly, we do not run an OpenID Connect server on behalf of our customers yet. This is on our roadmap and will be added soon, and there are definitely some services that we can't offer first-class integrations with until that happens. Your other point about "every language has an OAuth framework" is well-taken. Our initial launch used something proprietary and this was an issue, but we recently switched to spec-compliant JWTs to benefit more from existing libraries. Here's an example of our current, standard token: https://jwt.io/#token=eyJhbGciOiJSUzI1NiIsImtpZCI6Imluc18xcnJVREpyU0tDVlpiVWVnY2tmcWlrWFdQNzAiLCJ0eXAiOiJKV1QifQ.eyJleHAiOjE2MzY3MzAyMDQsImlhdCI6MTYzNjczMDE0NCwiaXNzIjoiaHR0cHM6Ly9jbGVyay41bWFwNi44ODFqbS5sY2wuZGV2IiwibmJmIjoxNjM2NzMwMTM0LCJzaWQiOiJzZXNzXzIwcDhQVm0xdE80NzJVd1had3htbkxDZXV2UiIsInN1YiI6InVzZXJfMjBwOFBVMTNwTWl6d1p2TnlNdVRrZEtEeTNSIn0.ZuOIFEnLQKjroGQrmuVc1BaeLHn23Gv4sRrQeoQ6BWDcvpU31q7a3WYxVNnfr6AOppthZ1ZEJMtlZsiOQ_AGvVgiMJBi9MtmlOFOk8ZRHfgADNouYyjUQJLEI_3AV9nY5VhUntG4vTDib7-7dA2DemhV7YVc64xJznaq-SvshdFftr7nVueB-28gBQSUFVkhcX_43m_AsjY9e_KMh9Le7FwgHCBlKRMH0cZMQlDAjY9yp1oD9ydrw41xLVwBLdex1SdMjH6r7LxBtv8dm2C2nRNlQkybUcsswYxgVF_w0DBGB6ViCN2xrgiC9qEfSQaSkjkY3KpEG5FeBMBbSqADBA https://jwt.io/#token=eyJhbGciOiJSUzI1NiIsImtpZCI6Imluc18xcn...