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

X (Twitter) refreshAccessToken #965

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

Originally created by @phanmn on GitHub (Apr 3, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

https://devcommunity.x.com/t/trying-to-get-oauth-2-0-token-receiving-missing-valid-authorization-header-error/163633

Current vs. Expected behavior

Current: Error “Missing valid authorization header”

Expected: Work

What version of Better Auth are you using?

1.2.5

Provide environment information

- Macos

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: false
  },
socialProviders: {
      twitter: {
        clientId: process.env.TWITTER_CLIENT_ID!,
        clientSecret: process.env.TWITTER_CLIENT_SECRET!,
        scope: ["tweet.read", "tweet.write", "offline.access", "users.read"]
      },
    },
});

Additional context

I have to add authentication: basic to custom refreshAccessToken to make it work

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: false
  },
socialProviders: {
      twitter: {
        clientId: process.env.TWITTER_CLIENT_ID!,
        clientSecret: process.env.TWITTER_CLIENT_SECRET!,
        scope: ["tweet.read", "tweet.write", "offline.access", "users.read"],
        refreshAccessToken: async (refreshToken) => {
          return refreshAccessToken({
            refreshToken,
            options: {
              clientId: process.env.TWITTER_CLIENT_ID!,
              clientSecret: process.env.TWITTER_CLIENT_SECRET!,
            },
            authentication: 'basic',
            tokenEndpoint: "https://api.twitter.com/2/oauth2/token",
          });
        },
      },
    },
});
Originally created by @phanmn on GitHub (Apr 3, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce https://devcommunity.x.com/t/trying-to-get-oauth-2-0-token-receiving-missing-valid-authorization-header-error/163633 ### Current vs. Expected behavior Current: Error “Missing valid authorization header” Expected: Work ### What version of Better Auth are you using? 1.2.5 ### Provide environment information ```bash - Macos ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: false }, socialProviders: { twitter: { clientId: process.env.TWITTER_CLIENT_ID!, clientSecret: process.env.TWITTER_CLIENT_SECRET!, scope: ["tweet.read", "tweet.write", "offline.access", "users.read"] }, }, }); ``` ### Additional context I have to add `authentication: basic` to custom `refreshAccessToken` to make it work ``` import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: false }, socialProviders: { twitter: { clientId: process.env.TWITTER_CLIENT_ID!, clientSecret: process.env.TWITTER_CLIENT_SECRET!, scope: ["tweet.read", "tweet.write", "offline.access", "users.read"], refreshAccessToken: async (refreshToken) => { return refreshAccessToken({ refreshToken, options: { clientId: process.env.TWITTER_CLIENT_ID!, clientSecret: process.env.TWITTER_CLIENT_SECRET!, }, authentication: 'basic', tokenEndpoint: "https://api.twitter.com/2/oauth2/token", }); }, }, }, }); ```
GiteaMirror added the bug label 2026-03-13 08:12:21 -05:00
GiteaMirror commented 2026-03-13 08:12:22 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 5, 2025):

Good catch! since it is a change from their side it does not actually require a change on our end. may be we will try to update the docs if necessary.

@Kinfe123 commented on GitHub (May 5, 2025): Good catch! since it is a change from their side it does not actually require a change on our end. may be we will try to update the docs if necessary.
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 bug
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#965
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?