archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: next-iron-session renamed to iron-session (#31292)

Browse source 
## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`
This commit is contained in:
Orri Arnarsson 2021-11-15 14:12:20 +00:00 committed by GitHub
parent 8c547139e4
commit 06d4bbbb24
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/authentication.md
View file

@ -119,7 +119,7 @@ Now that we've discussed authentication patterns, let's look at specific provide
If you have an existing database with user data, you'll likely want to utilize an open-source solution that's provider agnostic.
- If you want a low-level, encrypted, and stateless session utility use [`next-iron-session`](https://github.com/vercel/next.js/tree/canary/examples/with-iron-session).
- If you want a low-level, encrypted, and stateless session utility use [`iron-session`](https://github.com/vercel/next.js/tree/canary/examples/with-iron-session).
- If you want a full-featured authentication system with built-in providers (Google, Facebook, GitHub…), JWT, JWE, email/password, magic links and more… use [`next-auth`](https://github.com/nextauthjs/next-auth-example).
Both of these libraries support either authentication pattern. If you're interested in [Passport](http://www.passportjs.org/), we also have examples for it using secure and encrypted cookies: