github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 05:39:49 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #1523] [Feature Request] Authentication-Rule Sets #10699

New Issue
Closed
opened 2026-05-06 14:33:28 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-06 14:33:28 -05:00
Owner
Copy Link

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.)

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.)
GiteaMirror commented 2026-05-06 14:33:32 -05:00
Author
Owner
Copy Link

@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.
GiteaMirror commented 2026-05-06 14:33:33 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Sep 27, 2025):

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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#10699
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?