This should help.. https://docs-beta.prisma.io/1.13/operate-prisma-server/authentication-and-security-kke4/

I’ve followed this example fairly directly: https://github.com/develomark/prisma-now

and I only changed the user value in their example, to match the user in my actual database

I didn’t realize the deploy command made those settings active

that didn’t help anything…when I deployed to Now, it made the playground available at this URL: https://shuri-prisma-kqopyarpoc.now.sh/

(that’s hooked up to a test database with almost zero data)

but I can still query there without any credentials

I even tried hard-coding the values in to my .yml file, instead of having the

Dockerfile

drop them in via

sed

, and got the same result.

wait! nevermind…the deploy fixed it after all, I just didn’t notice the error the first time I ran it—once I got it to run successfully, I’m getting a “our token is invalid. It might have expired or you might be using a token from a different project.” response — yay! Might be worth putting something in the docs about how you need to do a

prisma deploy

before seeing any changes to the management API secret take effect