Public/Private view about gatus

[TwiN]

Good idea - enabling authentication via security.basic or security.oidc could be tweaked so that:

• If all endpoints are private, use the current login behavior
• If some endpoints are private, but not all, show a login button somewhere on the dashboard
• If no endpoints are marked as private, use the current login behavior (for backward compatibility)

---

Unrelated, but I'd like to thank you for creating a feature request despite having only used Gatus for an hour :)

[ivan-zaitsev]

@TwiN It would be good to have a feature to restrict specific group based on security. For example in OIDC there is a claim called groups which can be used for this feature. For basic security I suppose it can be resolved by creating multiple credentials which would have different groups assigned. Currently it is only possible to achieve this by deploying different instances of application per group.

---

For example:

Basic:

security:
  basic:
    users:
      - username: "gatus-username"
        password: "..."
        groups: ["gatus-group1", "gatus-group2"]

---

OIDC:

Sometimes token group can be represented as UUID or as resource URI, to make it more flexible group-mappings can be added to map token groups to Gatus groups.

security:
  oidc:
    groups-claim: "groups"
    groups-mappings:
      gatus-group1: token-group-1
      gatus-group2: token-group-2

---

Also either not included groups should be by default public, or it is even more secure to make all groups by default secure and create different section for non-authenticated users.

Public:

security:
  public:
    groups: ["gatus-group3"]

[jangrewe]

Yes, you summarized it exactly how i would love to see it! 😃
By now i'v been using Gatus for >2 weeks already, and there are some other minor feature requests mentioned in the "introduction" discussion (especially a toggle "show only unhealthy/healthy/all), but this feature to make a Gatus instance semi-private is my biggest wishlist item. 😍