Authentik outpost with cache or a read-only replica.

[gbdlin]

Hello, I'm trying to use authentik in an environment where we have multiple physical locations with some of them sometimes going offline for a prolonged time. Due to that, I cannot rely on every location contacting a centralized authentik server, especially that it will also be used for physical access control.

What I'm looking for is a way to preferably set up some outposts that do keep a cache of the whole user database which can be used when there is no connection to the main server. There is no need to have any management over those interfaces (especially that it would introduce a split-brain issue over time), being read-only for them is perfectly fine.

Is there anything in the authentik ecosystem that would allow for that? I've seen some cache settings available in the outposts, but it is not clear which auth schemes do use it and how it exactly works. Any help in would be appreciated.

[BeryJu]

The only outpost that has the ability to hold a full copy of the users in memory is the LDAP outpost, all other outposts require authentik to be available and read-writeable to authenticate