Jamil
Jamil
It would be great if this operated in a zero-downtime manner so that Admins can spin up new Gateways in an instance group without service interruption to users with active...
Refs #2654
Aiming to start prototyping this, hidden with a feature flag. I think we need a better UX than simply allowing `0.0.0.0/0` or `::/0` to be entered as a Resource. Perhaps...
## Update Currently testing how well this works today: - [ ] Apple: mostly works as-is. Network roaming breaks internet. - [ ] Android: packet loop -- `fd00:2021:1111:8000:100:100:111:0Unknown resource` -...
Also need the ability to allow users to disable Resources, otherwise this can cause unexpected consequences with Policy conditions. This can work as follows: - [ ] Add boolean `allow_disabling`...
Maybe we can just make this an `update_resources` call from app -> connlib like so: `session.update_resources([{"resource_id": "...", "disabled": true}])` Only resources that are that list should be updated, and resources...
Hm, perhaps it could work like this: - Session expiration: 4 hours - Auto-extend session on liveview navigations and full page loads (user activity) - **Always** require re-auth for sensitive...
Cc @rbhitchcock
Discussion w/ @rbhitchcock this morning (8/4/23) -- - Re: UX vs security -- **Bias towards usability**: Session token leaking is easy to prevent -- can use remote IP, user agent...
> IP for the client Yeah, for clients region is more appropriate, fairly popular request on discovery calls (can be post-1.0) > it will be incorrect to increase it Not...