Stijn de Witt

## ~~Workaround~~ Add `originEnvKey: 'AUTH_ISSUER'` to the `auth` key in *nuxt.config.ts*: ```ts auth: { originEnvKey: 'AUTH_ISSUER', provider: { type: 'authjs', defaultProvider: 'keycloak', }, }, ``` I just checked that, at...

Thanks for your detailed response. I have to add that after writing my last comment, I found out an extra source of confusion, which is that when we modify `.env`,...

Yeah ok. > Schedule renaming of AUTH_ORIGIN to AUTH_BASE_URL and originEnvKey to baseURLEnvKey to be included into 0.11 I missed that you also propose changing `originEnvKey`. That is a good...

IIRC, the reason this was not working was that the code that was checking process.env for `AUTH_ORIGIN` was in Auth JS itself, so it knew nothing about NUXT... and the...

Yes I thought so. So I think now, Nuxt-Auth can choose any name they want. So I would recommend choosing a name prefixed with `NUXT_` so as to be in...

Quickly checking your report and I even get a Typescript error when I add the Dutch translation but not the english one: ```console Property 'requiredFields' is missing in type '{...

I am seeing the same thing. Realm Config: ```tf resource "keycloak_realm" "myrealm" { ... security_defenses { headers { x_frame_options = "" } } } ``` `plan` output: ```sh # keycloak_realm.myrealm...