question: Is it possible to persist sessions across authcrunch container restarts?

[EricZimmerman]

when i restart docker container i have to reauth. this isnt a huge deal, but i was curious if its possible to have sessions persist across restarts?

[greenpau]

when i restart docker container i have to reauth. this isnt a huge deal, but i was curious if its possible to have sessions persist across restarts?

@EricZimmerman , at the moment it is not persistent. I had plans long time ago to implement "authdb" concept. The idea was to take "local" database setup and make it the center of identity management. The oauth and saml identity providers will be connected to it. The keys for each user will be unique. This way you can store and reset user session info centrally.

Unfortunately, I never had the time (nor that there is much demand) to do it.

[greenpau]

@EricZimmerman , I could probably add basic state management file. I need to check what is the caddy way to detect shutdown and dump state info.

When you shutdown your containers, do you see the log messages with proper “Byeee” in them? i.e. clean shutdown

[greenpau]

@EricZimmerman , the state will likely be kept in a directory structure of some sorts, i.e. not a single file. How would you configure configure your docker compose? i.e. mapping of read/write outside container dir from inside the container.

[EricZimmerman]

I use local directories vs docker volumes

/data/caddy:config

Etc

That way I can deal with backups and whatever via data/caddy on my file system

[greenpau]

I use local directories vs docker volumes

@EricZimmerman, just to confirm, you do not use docker volumes. Rather, you use local directories. Say you have 2 caddy containers running, will they point at their own unique directories? What I am getting to is how to avoid 2 instances hitting the same state management directory.

That way I can deal with backups and whatever via data/caddy on my file system

I need to read up on the /data/caddy. I vaguely recall there being some subtleties.

[EricZimmerman]

Yes I would save them to two different directories if I did two different containers.

Here is my paths:

volumes:
- /data/Caddyfile:/etc/caddy/Caddyfile
- /data/caddy/data:/data
- /data/caddy/config:/config

It works the same as docker volumes just without the docker management and it being in a different location under /var

[greenpau]

The reason one need to re-authenticate is because all the sessions cache.

The lookup happens here:

https://github.com/greenpau/go-authcrunch/blob/bf6ebd881b2257b71ee475da4c496e1abd7d46d4/pkg/authn/handle_http_portal.go#L45-L56

The cache gets created here:

https://github.com/greenpau/go-authcrunch/blob/bf6ebd881b2257b71ee475da4c496e1abd7d46d4/pkg/authn/portal.go#L223-L224

New sessions get added here.

https://github.com/greenpau/go-authcrunch/blob/bf6ebd881b2257b71ee475da4c496e1abd7d46d4/pkg/authn/handle_http_login.go#L354

Not sure how to persist the user.User at the moment, but will get there eventually.