connect-mongodb | SessionStorage for connect 's session middleware | Runtime Evironment library

Because your cookie is a httpOnly cookie so in order to send the cookie you can do by fetch method:

To connect to an external MongoDB, simply adjust the Windows Shell call to point to external address. Per MongoDB docs, mongo by itself defaults to localhost at port 27017. For a remote host, adjust these defaults.

Using connection string:

Going off the documentation, the saveUninitialized flag should be getting set to false -

Forces a session that is "uninitialized" to be saved to the store. A session is uninitialized when it is new but not modified. Choosing false is useful for implementing login sessions, reducing server storage usage, or complying with laws that require permission before setting a cookie. Choosing false will also help with race conditions where a client makes multiple parallel requests without a session. The default value is true, but using the default has been deprecated, as the default will change in the future. Please research into this setting and choose what is appropriate to your use-case.

https://github.com/expressjs/session#saveuninitialized

When you run Kafka Connect under Docker (including with the cp-kafka-connect-base) image it is usually in distributed mode. To create a connector configuration in this mode you use a REST call; it won't load the configuration from a flat file (per standalone mode).

You can either launch the container that you've created and then manually create the connector with a REST call, or you can automate that REST call - here's an example of doing it within a Docker Compose:

I found a solution. My Frontend was working on Liveserver, it is a Visual Studio Code extension. Probably that Liveserver somehow was blocking saving cookies on browsers. So I put the frontend server on express (I am not using any framework, just Vanilla Javascript) and now everything is working :)

Probably if I used framework like Vue or React I should not had been this problems. :)

Docker volumes are ephemeral, so this is expected behavior.

You need to mount host volumes for at least the Kafka and Zookeeper containers

e.g.

to install SMT it just the same as installing other connector,

Copy your custom SMT JAR file (and any non-Kafka JAR files required by the transformation) into a directory that is under one of the directories listed in the plugin.path property in the Connect worker configuration –

In your case copy to /usr/share/confluent-hub-components

Use the same options for the store and session on both. You'll need to have the same secret for both, so generate a cryptographically secure random string for that and pass it into both via environment variables (process.env).

It turns out that the problem was with the front end, not the back end, and it was a CORS issue. The express-session code was making the cookie just fine, but the front end couldn't accept it because having the back end hosted on port 3001 made it a cross-origin request (you'll recall the front end was on port 3000), even though both the front and back ends were on the same machine, localhost.

All I had to do was use the proxy field in my package.json file in my React project, like so: