starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #1223] [MERGED] Add steps for Google OAuth for OIDC #1972

New Issue
Closed
opened 2025-12-29 03:19:06 +01:00 by adam · 0 comments
adam commented 2025-12-29 03:19:06 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/1223
Author: @joshuataylor
Created: 2/22/2023
Status: ✅ Merged
Merged: 2/27/2023
Merged by: @juanfont

Base: main ← Head: feature/google-oauth-steps

📝 Commits (2)

📊 Changes

1 file changed (+31 additions, -0 deletions)

View changed files

📝 docs/oidc.md (+31 -0)

📄 Description

  • read the CONTRIBUTING guidelines
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • added unit tests
  • added integration tests
  • updated documentation if needed
  • updated CHANGELOG.md

I've been meaning to add this, as I was a little confused what the steps were for Google OAuth, and there are many differing solutions around. This is the easiest way to do things (and very obvious once you understand).

I also have screenshots of the process, but honestly it's pretty straight forward. The screenshots are just arrows to what to click on.

SCR-20230222-t4d SCR-20230222-t6i

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/1223 **Author:** [@joshuataylor](https://github.com/joshuataylor) **Created:** 2/22/2023 **Status:** ✅ Merged **Merged:** 2/27/2023 **Merged by:** [@juanfont](https://github.com/juanfont) **Base:** `main` ← **Head:** `feature/google-oauth-steps` --- ### 📝 Commits (2) - [`df320f8`](https://github.com/juanfont/headscale/commit/df320f8745f4f071ecc49faa6e75ccb93c193fe7) Add steps for Google OAuth for OIDC - [`d17d20f`](https://github.com/juanfont/headscale/commit/d17d20f66ba6021aa51af421e2ec9d81471e766c) Run prettier ### 📊 Changes **1 file changed** (+31 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/oidc.md` (+31 -0) </details> ### 📄 Description - [x] read the [CONTRIBUTING guidelines](README.md#contributing) - [ ] raised a GitHub issue or discussed it on the projects chat beforehand - [ ] added unit tests - [ ] added integration tests - [x] updated documentation if needed - [ ] updated CHANGELOG.md I've been meaning to add this, as I was a little confused what the steps were for Google OAuth, and there are many differing solutions around. This is the easiest way to do things (and very obvious once you understand). I also have screenshots of the process, but honestly it's pretty straight forward. The screenshots are just arrows to what to click on. <img width="259" alt="SCR-20230222-t4d" src="https://user-images.githubusercontent.com/225131/220628549-11ce7dc1-5399-4a34-9443-532954e960a5.png"> <img width="557" alt="SCR-20230222-t6i" src="https://user-images.githubusercontent.com/225131/220628562-2f6bd9b7-2963-4fd7-b507-51f6a9986ba9.png"> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 03:19:06 +01:00
adam closed this issue 2025-12-29 03:19:06 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1972
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?