Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

Database connection does not use SSL #52

Closed
ytsruh opened this issue Nov 7, 2022 · 3 comments
Closed

Database connection does not use SSL #52

ytsruh opened this issue Nov 7, 2022 · 3 comments
Assignees
Labels
back end Back end issue bug Something isn't working

Comments

@ytsruh
Copy link
Owner

ytsruh commented Nov 7, 2022

Azure MySQL Connect does not use SSL as the certificate couldnt be uploaded to Vercel. There seems to be a solution available here: prisma/prisma#11453

@ytsruh ytsruh added bug Something isn't working needs more information back end Back end issue labels Nov 7, 2022
@ytsruh ytsruh self-assigned this Nov 7, 2022
@ytsruh
Copy link
Owner Author

ytsruh commented Nov 12, 2022

@ytsruh
Copy link
Owner Author

ytsruh commented Nov 19, 2022

Solution is more effort than its worth. An SSL ceriticate would need to be used and there are two options:

  1. Deploy the certificate and read it as part of the file system. Would need to add to .gitignore and deploy manually/using cli to push the correct files to vercel. A .vercelignore file would need to be created to make sure that local .env is not pushed to vercel
  2. Read the certificate as a string but Prisma doesnt allow for this. Prisma requires a path to the .pem file & cannot currently use a string instead

Prisma connection string for MySQL - https://www.prisma.io/docs/concepts/database-connectors/mysql

@ytsruh
Copy link
Owner Author

ytsruh commented Nov 24, 2022

Closing this as not completed. Raised queries with both the vercel & prisma teams but there is only one workaround that is more effort than it is worth at this point

@ytsruh ytsruh closed this as completed Nov 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
back end Back end issue bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant