3 replies

OAuth plugin hooks

🤔QuestionOAuth related

I've been working with the OAuth plugin, and I noticed some of the requests done by the betterAuthClient use

application/json

application/json

contenType header as default when sending requests, but endpoints like

instrospect

instrospect

token

token

and

revoke

revoke

needs

application/x-www-form-urlencoded

application/x-www-form-urlencoded

; so doing

authClient.oauth.token(...)

authClient.oauth.token(...)

will return a

status code. I had to add the proper header inside the

fetchSetting

fetchSetting

headers object to make it work.

Would it make sense to override the headers through the

onRequest

onRequest

callback inside the OAuth plugin object configuration?

Something like:

    onRequest: async (ctx) => {
      if (
        ctx.method === "POST" &&
        (ctx.url.includes("/oauth2/introspect") ||
          ctx.url.includes("/oauth2/token") ||
          ctx.url.includes("/oauth2/revoke"))
      ) {
        ctx.headers.set("content-type", "application/x-www-form-urlencoded");
      }
    },

    onRequest: async (ctx) => {
      if (
        ctx.method === "POST" &&
        (ctx.url.includes("/oauth2/introspect") ||
          ctx.url.includes("/oauth2/token") ||
          ctx.url.includes("/oauth2/revoke"))
      ) {
        ctx.headers.set("content-type", "application/x-www-form-urlencoded");
      }
    },

Better Auth•3w ago•

3 replies

brk

OAuth plugin hooks

🤔QuestionOAuth related

I've been working with the OAuth plugin, and I noticed some of the requests done by the betterAuthClient use

application/json

application/json

contenType header as default when sending requests, but endpoints like

instrospect

instrospect

token

token

and

revoke

revoke

needs

application/x-www-form-urlencoded

application/x-www-form-urlencoded

; so doing

authClient.oauth.token(...)

authClient.oauth.token(...)

will return a

status code. I had to add the proper header inside the

fetchSetting

fetchSetting

headers object to make it work.

Would it make sense to override the headers through the

onRequest

onRequest

callback inside the OAuth plugin object configuration?

Something like:

    onRequest: async (ctx) => {
      if (
        ctx.method === "POST" &&
        (ctx.url.includes("/oauth2/introspect") ||
          ctx.url.includes("/oauth2/token") ||
          ctx.url.includes("/oauth2/revoke"))
      ) {
        ctx.headers.set("content-type", "application/x-www-form-urlencoded");
      }
    },

    onRequest: async (ctx) => {
      if (
        ctx.method === "POST" &&
        (ctx.url.includes("/oauth2/introspect") ||
          ctx.url.includes("/oauth2/token") ||
          ctx.url.includes("/oauth2/revoke"))
      ) {
        ctx.headers.set("content-type", "application/x-www-form-urlencoded");
      }
    },

OAuth plugin hooks

Similar Threads

OAuth plugin hooks

Similar Threads

Similar Threads

Similar Threads