mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[GH-ISSUE #607] Feature Request: Time Restrictions #156
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#156
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mathieumd on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/607
We (will) use Bastion to filter out access from our subcontractors to their servers in our infrastructure. We request them to only access at some planned day and time (for example, on 2026-01-15 from 09:00 to 18:00). Currently we schedule these times on a central firewall, but it's cumbersome.
Wouldn't it make sense for The Bastion to support access time restrictions?
By the way, I have the same question for originating IP address: shouldn't The Bastion support a way to restrict a given group/member to specific network?