Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add basic auth #1

Merged
merged 29 commits into from
Mar 25, 2024
Merged

Add basic auth #1

merged 29 commits into from
Mar 25, 2024

Conversation

delbaoliveira
Copy link
Collaborator

No description provided.

Copy link

vercel bot commented Mar 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
app-router-auth ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 25, 2024 1:50pm

- Move "use client" down from the page to the form
- Add try/catch to login
- fix ts errors
- display individual field errors
- remove client form validation (we want to display the errors from the server)
- add `useFormStatus`
@delbaoliveira delbaoliveira marked this pull request as ready for review March 25, 2024 13:51
@delbaoliveira delbaoliveira merged commit b3ffe78 into main Mar 25, 2024
2 checks passed
@delbaoliveira delbaoliveira deleted the add-basic-auth branch March 25, 2024 13:51
delbaoliveira added a commit to vercel/next.js that referenced this pull request Apr 16, 2024
Clarify best practices for implementing authentication in Next.js,
including what Next.js and React features to use and when. With the
minimum number of tools, we'll try to teach authentication from first
principles (simple password + email), then recommend Next.js-compatible
libraries, and further resources.

**Authentication:**
- [x] Forms and Server Actions
- [x] Server-side form validation and early returns
- [x] Form errors with `useFormStatus()`
- [x] Pending states with `useFormState()`

**Session Management:** 
- [x] Stateless Sessions
- [x] Database Sessions
- [x] Setting cookies on the server
  - [x] `cookies()`
- [x] `sever-only`

**Authorization:** 
- [x] Optimistic vs. secure checks
- [x] Middleware for optimistic checks
  - [x] Performance caveats - what not to do
- [x] DAL - centralizing data requests, verifying auth state close to
the data source
   - [x] `redirect()`
- [x] DTO - returning the minimum data, preventing exposure on the
client
- [x] Recommendations for: 
  - [x] Server Components
      - [x] Partial rendering and `layout` caveats
  - [x] Server Actions
  - [x] Route Handlers 
  
DX Content: ["What is the right way to do
authentication?"](https://www.notion.so/vercel/00b2a5121a264939a5d4d10f76b36954?v=cac009672f9d411f900f41a0c3971702&p=2a80e8d450f54ea58da5cf8b42c15ac1&pm=s).
Test Example: vercel-labs/app-router-auth#1

This is how I currently visualize it, this diagram is not meant for
users, but to help clarify our current understanding. What am I missing?

![CleanShot 2024-03-22 at 14 27
24@2x](https://github.com/vercel/next.js/assets/32464864/4bdfc0f5-a82d-4faa-bbf3-c15146d534c8)

---------

Co-authored-by: Michael Novotny <[email protected]>
Co-authored-by: Anthony Shew <[email protected]>
Co-authored-by: Lee Robinson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant