WIP: Removed keys from Next public config #1689
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
sergiomario
force-pushed
the
hotfix/exposed-keys
branch
from
0700a23 to
453f109
Compare
sergiomario
force-pushed
the
hotfix/exposed-keys
branch
from
453f109 to
9031297
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contexto
Algumas chaves privadas estão sendo impressas no HTML que fica acessível para o usuário final.
Essas chaves do Pagarme, os Tokens da API GraphQL e do Open API deveriam ser secretas. É necessário revisar a forma de como resolver isso, entendendo ser uma função da própria tecnologia NextJS e então atualizar as chaves de acesso aos serviços.
https://nextjs.org/docs/pages/api-reference/next-config-js/runtime-configuration