During signin, getSessionExp does not use token

[EtienneBruines]

This is my code:

const { signin } = useSurrealAuth()

await signin({
  NS: 'my-ns',
  DB: 'my-db',
  AC: 'user',
  username,
  password,
})

When successfully getting a token from the SurrealDB server (I got a result via DevTools), this token is not used by the subsequent SELECT exp FROM $session that is queried during getSessionExp. No Authorization HTTP request header is present for that RPC call.

I tried using DevTools Debugger to figure out where this is going wrong. It seems like the correct values (the Authorization header with the Bearer token) are being passed to the surrealFetch (within the surrealRPC function), but the onRequest handler seems to remove it.

nuxt-surrealdb/src/runtime/plugin.ts

Lines 20 to 32 in 2191857

	const surrealFetch = ofetch.create({
	onRequest({ options }) {
	const { baseURL, headers } = surrealFetchOptionsOverride(database, options)
	if (!baseURL) {
	createError({
	statusCode: 500,
	message: 'Missing SurrealDB URL',
	})
	}
	options.baseURL = baseURL
	options.headers = defu<HeadersInit, HeadersInit[]>(options.headers, { ...headers })
	},
	})

The result of surrealFetchOptionsOverride(database, options) does not contain the Authorization header any more. Ths is OK, because there is no auth preset defined.

When it then comes to the defu call, it cannot correctly handle options.headers being a fancy Headers object, where it cannot simply 'set' the header values. Thus, after the defu call, we're left with whatever was in headers (and not options.headers) - which is just the presets and not the options.headers (with token) that were passed along.

Potentially related: https://github.com/unjs/ofetch/releases/tag/v1.4.0

[sandros94]

Indeed that defu was something I was concerned about when reading the ofetch v1.4.0 release.

[sandros94]

I started working on this one first, and it basically breaks the whole module 🙄

[sandros94]

@EtienneBruines please feel free to reopen if you experience any more problems after updating to the latest v0.4.0 release 🙏