OAuth example should not infer org affiliation from the email field.

Open
#70 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
jupyter-notebook, python

Research direction

Start with oauth_example/oa.py at the linked line, then inspect nbs/explains/oauth.ipynb for the analogous email-based affiliation check. Search the example repository and explainer for other uses of the email field in access decisions. Done means both examples follow Google's hd claim guidance and no email-based organization inference remains.

Written by the indexing model from the issue text.

Description

This example parses the user's email, returned from Google's authorization server, in order to determine if the user should have access:

https://github.com/AnswerDotAI/fasthtml-example/blob/6a985a7d00ff33a54a07aa9ff9a8dba77bbeb428/oauth_example/oa.py#L9

However, Google says not to do this, and to use the "hd claim" instead:

Image

We should update the example to follow Google's advice.

An analogous change will also be needed in the fasthtml explainer notebook: https://github.com/AnswerDotAI/fasthtml/blob/main/nbs/explains/oauth.ipynb

It may appear elsewhere as well.

Dominant language
CSS
Stars
857
Forks
131
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AnswerDotAI/fasthtml-example

All issues in AnswerDotAI/fasthtml-example

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.