gatsbyjs/gatsby

SSR: Restricting Access to Specific Pages Based on Authenticated User

Open

#36427 opened on Aug 20, 2022

View on GitHub
 (7 comments) (2 reactions) (0 assignees)JavaScript (55,950 stars) (10,198 forks)batch import
help wantednot staletype: documentation

Description

Preliminary Checks

Summary

@KyleAMathews asked for this issue: https://github.com/gatsbyjs/gatsby/issues/1100#issuecomment-1221020314

A guide about how to perform simple authentication and authorization in Server-Side Rendering (SSR) using getServerData would be great!

I would suggest that it include the following:

  1. A page and related static images that are fully public (no authentication required) - eg. a login page
  2. A page and related static images that are accessible only to any logged-in user - eg. an index page
  3. A page and related static images that are accessible only to any admin user - eg. an admin dashboard page

Further background information / motivation:

Steps to Resolve this Issue

  1. Look for a guide for authentication / authorization for SSR in the Gatsby docs
  2. Fail in finding such a guide

Contributor guide

Tech stack
javascriptreactnodejs
Domain
documentationbackendsecurity
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Gatsby basicsReact knowledgeSSR conceptsAuthentication fundamentals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the existing Gatsby SSR documentation, especially the `getServerData` API. Look at the referenced issues (#1100, #32479) for background. Create a new guide in the docs folder with examples for public, logged in, and admin pages. Ensure the guide includes code snippets and images.