New Nuxt /api/access endpoint causing issues
Today I went and updated my
Also, unlike the other endpoints I can't see any documentation on this new endpoint.
Now in my setup I have a global catch-all
What is strange is that the other Kinde SDK endpoints do not trigger the proxy. (E.g.
I've tried to bypass this by getting my catchall file to either return
@nuxtjs/kinde package from 0.1.11 to 0.2. All of a sudden all of my routes were failing as they were trying to access /api/access which I'd never seen before and isn't one of my routes. I eventually found the route in the source code of your Nuxt SDK.Also, unlike the other endpoints I can't see any documentation on this new endpoint.
Now in my setup I have a global catch-all
[..].ts file which I use as a proxy between Nuxt and my .NET API. It's job is basically to take the user's request pointing to my Nuxt server and via a Nitro proxy redirect it to my .NET API and add the Kinde bearer token to the header.What is strange is that the other Kinde SDK endpoints do not trigger the proxy. (E.g.
/api/login, /api/logout /api/health. They go through your SDK normally. Is it possibly because they are GET methods, whereas this is a POST method?I've tried to bypass this by getting my catchall file to either return
undefinedsendProxy but it either returns no data (which isn't expected) or gives a bad gateway issue. I'll admit that this is possibly more an issue on my end around lack of knowledge of Nuxt / Nitro but I'd appreciate it if someone has a solution.