github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

feat: request additional scopes from user #501

New Issue
Closed
opened 2026-03-13 07:50:05 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 07:50:05 -05:00
Owner
Copy Link

Originally created by @sudipbuilds on GitHub (Dec 31, 2024).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Hey! I'm currently working on an app that requires users to grant access to their GitHub repositories to function properly. I know additional scopes can be added to better-auth's configuration during user sign-up. However, users might not want to grant repository access on their first visit.

import { betterAuth } from "better-auth";

export const auth = betterAuth({
  appName: "Auth Test",
  socialProviders: {
    github: {
      clientId: process.env.GITHUB_CLIENT_ID!,
      clientSecret: process.env.GITHUB_CLIENT_SECRET!,
      scope: ["repo"], // additional scopes apart from which are used by default for retrieving common user information
    },
  },
});

Describe the solution you'd like

I would like a flow where even if additional scopes are not written in the config, I should be able to request those post sign-up when needed. An example of this can be -

async function getGithubAccess() {
  await authClient.signIn.social(
    { provider: "github" },
    { scopes: ["repo"] }
  );
}

<button onClick={getGithubAccess}>Give access to your github repositories</button>

Also update the access token and refresh token in database.

Describe alternatives you've considered

Using Clerk, this can be achieved using the component by passing additionalOAuthScopes prop, but it doesn’t offer much control.

Source - https://clerk.com/docs/authentication/social-connections/oauth#request-additional-o-auth-scopes-after-sign-up

Additional context

No response

Originally created by @sudipbuilds on GitHub (Dec 31, 2024). ### Is this suited for github? - [ ] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Hey! I'm currently working on an app that requires users to grant access to their GitHub repositories to function properly. I know additional scopes can be added to better-auth's configuration during user sign-up. However, users might not want to grant repository access on their first visit. ```ts import { betterAuth } from "better-auth"; export const auth = betterAuth({ appName: "Auth Test", socialProviders: { github: { clientId: process.env.GITHUB_CLIENT_ID!, clientSecret: process.env.GITHUB_CLIENT_SECRET!, scope: ["repo"], // additional scopes apart from which are used by default for retrieving common user information }, }, }); ``` ### Describe the solution you'd like I would like a flow where even if additional scopes are not written in the config, I should be able to request those post sign-up when needed. An example of this can be - ```ts async function getGithubAccess() { await authClient.signIn.social( { provider: "github" }, { scopes: ["repo"] } ); } <button onClick={getGithubAccess}>Give access to your github repositories</button> ``` Also update the access token and refresh token in database. ### Describe alternatives you've considered Using Clerk, this can be achieved using the <UserButton /> component by passing `additionalOAuthScopes` prop, but it doesn’t offer much control. Source - https://clerk.com/docs/authentication/social-connections/oauth#request-additional-o-auth-scopes-after-sign-up ### Additional context _No response_
GiteaMirror commented 2026-03-13 07:50:06 -05:00
Author
Owner
Copy Link

@arthberman commented on GitHub (Dec 31, 2024):

+1

@arthberman commented on GitHub (Dec 31, 2024): +1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#501
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?