8000 README.md: update required scopes for oauth clients by sebpretzer · Pull Request #182 · tailscale/github-action · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

README.md: update required scopes for oauth clients #182

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sebpretzer
Copy link

The guidance provided for the proper scopes for oauth clients is incomplete. It only includes the auth_keys scope, but any oauth client using this github action should also include all:read and devices:core. This follows the suggestion provided in #100 (comment).

I have attempted to follow the contributing guidelines found in commit-messages.md.

Note: The documentation on tailscale's website will need to be updated as well.

Document the `all:read` and `devices:core` required scopes discussed in tailscale#100

Signed-off-by: Seb Pretzer <24555985+sebpretzer@users.noreply.github.com>
@mpminardi
Copy link
Member

Hey @sebpretzer ! Were you seeing errors or failures when using the action without all:read and devices:core? auth_keys should be all that is needed to have the action minimally work with a node joining the target tailnet.

I've put up #183 which added a second OAuth client to our test suite with just the auth_keys scope specified and nodes created with this client are successfully joining our test tailnet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0