next-auth-example VS zenstack

https://github.com/nextauthjs/next-auth-example https://next-auth.js.org/getting-started/example https://next-auth.js.org/configuration/initialization#route-handlers-app https://www.prisma.io/docs/getting-started/quickstart https://authjs.dev/reference/adapter/prisma

This is not true in the slightest. Just one example: https://github.com/nextauthjs/next-auth-example/blob/main/components/footer.tsx

Looking at the example repo for using next-auth (https://github.com/nextauthjs/next-auth-example), how would I add a provider to the [...auth].ts file so that I could have a user login with email and password, hit my FastAPI authentication endpoint, and resolve with the token if authentication is successful? Do I just use the Credentials Provider? https://next-auth.js.org/configuration/providers/credentials

If you want a full-featured authentication system with built-in providers (Google, Facebook, GitHub…), JWT, JWE, email/password, magic links, and more… use [next-auth](https://github.com/nextauthjs/next-auth-example).

Just use (next-auth)[https://github.com/nextauthjs/next-auth-example], and without setting up a db it automatically defaults to JWTs. Only thing that I would do is make sure to setup a revocation policy on the server that allows you to revoke JWTs before its expiration. I usually keep a simple json document of revoked tokens, which I can then deny access to in-case the token was ever compromised.

I see in the official example app,

First we need to clone example app from next-auth. You can find the whole guide from next-auth here or just follow my steps.

The gist of it is actually covered by the next-auth example app: https://github.com/nextauthjs/next-auth-example/blob/main/pages/api/examples/protected.js

Support for Polymorphic Associations #430

Another strategy is to model access control declaratively and enforce it in the application layer. ZenStack (built above Prisma ORM) and Hasura are good examples of this approach. The following code shows how access policies are defined with ZenStack and how a secured CRUD API can be derived automatically.

ZenStack is a toolkit built above Prisma that adds access control, automatic CRUD web API, etc. It unleashes the ORM's full power for full-stack development.

We need to have some concrete language to build to help make sense of things. I always felt real-world examples are much more effective than toys, so I'll use the ZModel language that we're building at ZenStack as an example. It's a DSL used to model database tables and access control rules. To keep the post short, I'm going only to use a small set of features to demonstrate. Our goal will be to compile the following code snippet:

It's assumed that you know the basics of using Prisma. Prisma is an excellent ORM. But it doesn't have a built-in authorization solution. To supplement that, we'll use ZenStack throughout the samples. ZenStack is a toolkit that supercharges Prisma in many ways. One of the features is to provide a declarative way to model authorization. Its modeling language, ZModel, is a superset of Prisma Schema Language, so it should be easily understandable to people familiar with Prisma.

[Feature Request] Support for Polymorphic Associations #430

ZenStack takes a unique approach and solves the problem at a slightly higher level: the ORM. It is implemented above Prisma ORM and supports a wide variety of databases. It extends Prisma to allow modeling access policies inside the data schema and enforces them at runtime by injecting into Prisma queries.

If you generate Prisma queries as we do here, you can inject extra filtering conditions into the generated query object. Here's the nice thing: ZenStack can do it automatically for you.

ZenStack for automatic enforcement of access control. ZenStack is a toolkit that extends Prisma ORM to allow you to model access policies and data schema in one place.