It would be nice to be able to create Authentication-Rule Sets, so that when establishing rules on multiple resources, one doesn't have to manually recreate all the authentication settings and rules settings.
e.g.
Suppose I have 20 resources. I want each of these resources to:
not use Platform SSO;
use the same whitelisted emails
always allow certain IPs
pass all other IPs to auth
If there was the ability to create an Authentication-Rule Set, this could be applied to resources when created, rather than having to create each of these settings for each resource.
Also, perhaps allow overriding of the Authentication-Rule Set, if a custom setting is set on a resource. (Thinking, for example, having a rule set that includes Password authentication, but one wants a different password for resources, but everything else should be the same.)
Originally created by @curious-debug on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1523
It would be nice to be able to create Authentication-Rule Sets, so that when establishing rules on multiple resources, one doesn't have to manually recreate all the authentication settings and rules settings.
---
e.g.
Suppose I have 20 resources. I want each of these resources to:
- not use Platform SSO;
- use the same whitelisted emails
- always allow certain IPs
- pass all other IPs to auth
If there was the ability to create an Authentication-Rule Set, this could be applied to resources when created, rather than having to create each of these settings for each resource.
Also, perhaps allow overriding of the Authentication-Rule Set, if a custom setting is set on a resource. (Thinking, for example, having a rule set that includes Password authentication, but one wants a different password for resources, but everything else should be the same.)
@Pallavikumarimdb commented on GitHub (Sep 23, 2025):
This is a great feature suggestion! Having Authentication-Rule Sets that can be reused across resources would definitely make setup and management much easier.
For the “always allow certain IPs” part - already working on this in #1248 and will make it possible to add more as needed.
<!-- gh-comment-id:3322211085 -->
@Pallavikumarimdb commented on GitHub (Sep 23, 2025):
This is a great feature suggestion! Having Authentication-Rule Sets that can be reused across resources would definitely make setup and management much easier.
For the “always allow certain IPs” part - already working on this in #1248 and will make it possible to add more as needed.
Thanks, converting this to a discussion thread so others can upvote and participate!
<!-- gh-comment-id:3341944672 -->
@miloschwartz commented on GitHub (Sep 27, 2025):
Thanks, converting this to a discussion thread so others can upvote and participate!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @curious-debug on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1523
It would be nice to be able to create Authentication-Rule Sets, so that when establishing rules on multiple resources, one doesn't have to manually recreate all the authentication settings and rules settings.
e.g.
Suppose I have 20 resources. I want each of these resources to:
If there was the ability to create an Authentication-Rule Set, this could be applied to resources when created, rather than having to create each of these settings for each resource.
Also, perhaps allow overriding of the Authentication-Rule Set, if a custom setting is set on a resource. (Thinking, for example, having a rule set that includes Password authentication, but one wants a different password for resources, but everything else should be the same.)
@Pallavikumarimdb commented on GitHub (Sep 23, 2025):
This is a great feature suggestion! Having Authentication-Rule Sets that can be reused across resources would definitely make setup and management much easier.
For the “always allow certain IPs” part - already working on this in #1248 and will make it possible to add more as needed.
@miloschwartz commented on GitHub (Sep 27, 2025):
Thanks, converting this to a discussion thread so others can upvote and participate!