Timed / Scheduled Authentication (and more)

[felinusfish]

Summary

Currently, authentication has to be manually enabled and disabled. I'm sure there are third-party solutions for creating a scheduled authentication, but it'd be great for the ability to easily create schedules for turning on and off certain features on a resource. Along with this, having timed authentication would be great for things such as giving temporary access to a friend group via PIN potentially until a certain time, or for a length of period.

Motivation

This would solve the following situations:

• You have planned maintenance, but still want to have direct access to the resource via Platform SSO.
• Your friends want to access a resource, so you provide them with temporary access via PIN or password.
• There is a resource that you want to open during certain times to the public, and keep closed behind authentication. (any connections should be forcibly closed as well, if they aren't already)

I imagine there are many other use cases, especially if it extended beyond authentication and enabling/disabling the resource. For example, rules (and the individual rules themselves) should also be allowed to be scheduled so that they can be disabled or enabled as well.

Proposed Solution

I would add a "Schedules" tab in the resource, alongside adding a new sidebar element called "Scheduling" that could potentially be combined with Blueprints, since I imagine a schedule could technically be created using the blueprints feature? Although, definitely not as easily.

Then, within the Schedules tab, have it display names for schedules, along with the ability to enable and disable them, delete them, or edit them directly. Once you start editing them, you get a menu that allows you to check for certain parameters, e.g. If "time is after 8pm AND time is before 10am" then "enable Platform SSO authentication" else (optional) "disable Platform SSO authentication"

Alternatives Considered

The workaround is to use blueprints, I would imagine, but they aren't very easy to use and I'd assume especially for enterprise users, they'd benefit massively from easily configurable timed authentication and scheduling (especially for maintenance durations).

Additional Context

If variables you might want to add:

• Date
• Time
• Health Check Fails / Succeeds