Frederic Jahn

The new `hanko-client.js` file should be included in the hanko-js `Dockerfile`, so we can use the client later in the example app and it will work in the docker compose...

Thank you for your contribution. Unfortunately this solution does not work. The problem with it is, that koanf does not return an error if keys can't be mapped. So the...

We would also need to change it in the session middleware: https://github.com/teamhanko/hanko/blob/a6f677ad680bfc6796e159265d0c7cb9f9f32988/backend/server/middleware/session.go#L13

Looks like we always validate the complete config, although we only need to validate the database part of the config for the `migrate` command. So we should only validate the...

The `wellKnownHandler` must also be available under the configured path prefix otherwise the frontend could not get the config. Also when the statusHandler in the public router is affected by...

Having another prefix only for the `well-known` route can become complex to configure, because you must also change the frontend-sdk and configure it correctly. Currently it uses the base-url (given...

@FerdinandvHagen I thought a little bit more about this, maybe we can add a new config option (e.g. `path_prefix_affects_well_known: true`) which defaults to `true`. When it is set to `false`...

I would say yes, you can delete a user with transactions but I also think we need a way to get those transaction data. Then we can show (e.g. in...

> So we want to ignore that provider after the warning? Yes