Skip to content

Week 7 — OAuth2 & NextAuth

May 12 – May 16

What We're Covering

OAuth2 and federated identity — how modern apps handle login without managing passwords. You'll learn the authorization code flow and integrate NextAuth into a Next.js app using the shared auth service.

Readings

Due This Week

Check-Off 7: Next.js Foundations — Due: Sunday, May 17 at 11:59 PM

Canvas · Site

Complete the introduction + Chapters 1–5 of the official Next.js Learn dashboard course.

Sprint 5 — Due: Sunday, May 17 at 11:59 PM

Canvas · Site

Bug Tracker front-end — Next.js app with a public report form on top of your own API's POST /issues. No auth; small ramp into Next.js. Deployed.

What You Should Be Working On

  • Sprint 5 — build the Bug Tracker front-end: a public report form on top of your own API's POST /issues. No authentication. Small single-sprint FE deliverable focused on Next.js fundamentals. Your downstream partner group uses this to file bugs against you during Sprints 6–8.
  • Week 7 check-off — details TBD.
  • Review the Next.js guide — Next.js covers the framework you'll use for the front-end sprints.
  • No reading or quiz this week — the OAuth2 reading is in Week 8.
  • AI Diary — log your Week 7 entry.

Learning Objectives & Course Outcomes

Syllabus Learning Objectives addressed this week:

  • LO3: Implement authentication and authorization using token-based and federated identity patterns
  • LO4: Build interactive front-end applications using a component-based framework
  • LO7: Collaborate in teams using version control workflows, sprint milestones, and code review

Course Outcomes:

  • Inquiry and Critical Thinking — modes of inquiry, analysis, and critical synthesis

Lecture Recaps

  • Tuesday — Coming soon
  • Thursday — Coming soon