feat(core): detect NEXTAUTH_SECRET
#3783
Merged
Conversation
This file contains hidden or 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
|
🎉 Experimental release published on npm! npm i [email protected]yarn add [email protected] |
This was referenced Feb 2, 2022
2 tasks
balazsorban44
pushed a commit
that referenced
this pull request
Apr 5, 2022
* docs: Update JWT docs to reflect JWE changes in v4 This PR #3039 changed the defaults for JWT tokens to be encrypted by default (JWE). We have conflicting documentation across the docs site and readme. Additionatlly this PR #3783 made providing a secret required in production via NEXTAUTH_SECRET or an option. * Missed a reference * Update docs/docs/faq.md Co-authored-by: Nico Domino <[email protected]> * Update docs/docs/faq.md Co-authored-by: Nico Domino <[email protected]> Co-authored-by: Nico Domino <[email protected]>
mnphpexpert
added a commit
to mnphpexpert/next-auth
that referenced
this pull request
Sep 2, 2024
* feat(core): detect `NEXTAUTH_SECRET` env variable * chore(dev): use detected `NEXTAUTH_SECRET` in dev app
mnphpexpert
added a commit
to mnphpexpert/next-auth
that referenced
this pull request
Sep 2, 2024
* docs: Update JWT docs to reflect JWE changes in v4 This PR nextauthjs#3039 changed the defaults for JWT tokens to be encrypted by default (JWE). We have conflicting documentation across the docs site and readme. Additionatlly this PR nextauthjs#3783 made providing a secret required in production via NEXTAUTH_SECRET or an option. * Missed a reference * Update docs/docs/faq.md Co-authored-by: Nico Domino <[email protected]> * Update docs/docs/faq.md Co-authored-by: Nico Domino <[email protected]> Co-authored-by: Nico Domino <[email protected]>
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.
Since v4, we have made providing a secret mandatory in production. The
NextAuthconfiguration (in[...nextauth].js) required either the top-levelsecretorjwt.secretvalues to be set, otherwise an error is thrown. https://next-auth.js.org/errors#no_secretTo make this configuration easier (which ties in with #3657), we are going to detect if you set a
NEXTAUTH_SECRETvariable automatically, so it is less likely that you end up with the above error.Reasoning 💡
Checklist 🧢
Affected issues 🎟