Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix: allow orgs with default github provider (cherry-pick #16755)#16784

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
stirby merged 1 commit intorelease/2.20fromcherry-pick-537e9b-release/2.20
Mar 3, 2025

Conversation

gcp-cherry-pick-bot[bot]
Copy link

Cherry-picked fix: allow orgs with default github provider (#16755)

This PR fixes 2 bugs:

Problem 1

The server would fail to start when the default github provider was
configured and the flag--oauth2-github-allowed-orgs was set. The
error was

error: configure github oauth2: allow everyone and allowed orgs cannot be used together

This PR fixes it by enabling "allow everone" with the default provider
only if "allowed orgs" isn't set.

Problem 2

The default github provider uses the device flow to authorize users, and
that's handled differently by our web UI than the standard oauth flow.
In particular, the web UI only handles JSON responses rather than HTTP
redirects. There were 2 code paths that returned redirects, and the PR
changes them to return JSON messages instead if the device flow is
configured.

This PR fixes 2 bugs:## Problem 1The server would fail to start when the default github provider wasconfigured and the flag `--oauth2-github-allowed-orgs` was set. Theerror was```error: configure github oauth2: allow everyone and allowed orgs cannot be used together```This PR fixes it by enabling "allow everone" with the default provideronly if "allowed orgs" isn't set.## Problem 2The default github provider uses the device flow to authorize users, andthat's handled differently by our web UI than the standard oauth flow.In particular, the web UI only handles JSON responses rather than HTTPredirects. There were 2 code paths that returned redirects, and the PRchanges them to return JSON messages instead if the device flow isconfigured.
@stirbystirby merged commit6da3c9d intorelease/2.20Mar 3, 2025
32 checks passed
@stirbystirby deleted the cherry-pick-537e9b-release/2.20 branchMarch 3, 2025 23:49
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsMar 3, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@stirbystirbystirby approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@stirby@hugodutka

[8]ページ先頭

©2009-2025 Movatter.jp