Next.js basePath handling

[RokoTechnology]

I am running OpenFAAS based setup with multiple servers on different sub paths of same domain - mydomain.com/function/app1, mydomain.com/function/app2 etc.

Now i'm trying to set up a Next + Ory app at mydomain.com/function/nextapp

I am using Next.js 12 with @ory/client 1.1.4 and @ory/integrations 1.1.0

• I have configured my pages/api/.ory/[...paths].js as suggested at https://github.com/ory/integrations#nextjs
• I have configured my pages/index.js session detection try/catch and router.push redirect as suggested at https://www.ory.sh/docs/getting-started/integrate-auth/nextjs
• I have verified I have ORY_SDK_URL set up properly in my environment

I have a basePath: '/function/nextapp' in my next.config.js because I need the ory login pages to live on mydomain.com/function/nextapp/api/.ory/ui/login instead of mydomain.com/api/.ory/ui/login

Unfortunately, no matter what I try, I always end up being redirected to mydomain.com/api/.ory/ui/login?flow=...

• I tried manually going to the URL mydomain.com/function/nextapp/api/.ory/ui/login
• I tried explicitly redirecting the user to the absolute url such as router.push('mydomain.com/function/nextapp/api/.ory/ui/login')
• I tried explicitly overriding the edgeConfig.basePath to /function/nextapp/api/.ory/ when instantiating FrontendApi such as new FrontendApi(new Configuration({ basePath: 'mydomain.com/function/nextapp/api/.ory/ui/login' }))

Looks like the currently suggested Next + Ory setup ignores the next.config.js basePath and it is not possible to override it manually either.
Looks like the FrontendApi ignores edgeConfig and always redirects to the root relative basePath /api/.ory/ui/login

[RokoTechnology]

actually, i think the root cause is not in the FrontendApi but in the @ory/integrations/next-edge here

integrations/src/next-edge/index.ts

Line 178 in 84858ea

"/api/.ory",

[RokoTechnology]

i made a PR which should resolve my issue. you could pass appBasePath: myNextConfig.basePath to the createApiHandler