Slackbot
05/26/2018, 7:33 PMalechp
05/26/2018, 7:34 PMalechp
05/26/2018, 7:36 PMThe disableAuth property has been removed. If you don't want your Prisma API to require authentication, simply omit the secret property.
alechp
05/26/2018, 7:39 PMprisma token
to confirm Prisma doesn’t think a secret is set
---
Manually checked the following as well:
✔️ No secret in .env
✔️ No secret in prisma.yml (and disableAuth has been removed)
✔️ No secret in docker-compose.yml
✔️ No secret in index.js (Prisma server initialization)
✔️ No secret in ~/.prisma/config.ymlalechp
05/26/2018, 7:40 PM{
"data": null,
"errors": [
{
"message": "Your token is invalid. It might have expired or you might be using a token from a different project.",
"locations": [],
"path": [
"foos"
],
"code": 3015,
"requestId": "local:api:cjhnstuyl00070950v5gt58hx"
}
]
}
alechp
05/26/2018, 7:40 PMalechp
05/26/2018, 7:45 PMAngel
05/26/2018, 10:28 PMnilan
05/28/2018, 8:59 AMAngel
05/29/2018, 12:57 AM// secret: process.env.PRISMA_SECRET
in index.js and in database/prisma.yl and now it works, but if they are uncommented throw that errornilan
05/29/2018, 8:10 AMprocess.env.PRISMA_SECRET
and the secret in prisma.yml
match?alechp
05/29/2018, 9:49 PMAngel
05/30/2018, 3:16 AM