[GH-ISSUE #3636] How to limit the client only can access specified ports by OIDC. #2901

Closed
opened 2026-05-05 13:52:25 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @bnuzhouwei on GitHub (Sep 30, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3636

Describe the feature request

OIDC is a useful feature to validate clients so that some clients can be disabled as wish.

But how to limit the client only can access specified ports?

i.e limit the ports and service count in the server.

Describe alternatives you've considered

When oidc auth, send ports and client ak, sk together, so that we can custom the OIDC server to determine whether sending id_token or not.

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @bnuzhouwei on GitHub (Sep 30, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3636 ### Describe the feature request OIDC is a useful feature to validate clients so that some clients can be disabled as wish. But how to limit the client only can access specified ports? i.e limit the ports and service count in the server. ### Describe alternatives you've considered When oidc auth, send ports and client ak, sk together, so that we can custom the OIDC server to determine whether sending id_token or not. ### Affected area - [X] Docs - [ ] Installation - [ ] Performance and Scalability - [X] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:52:25 -06:00
Author
Owner

@fatedier commented on GitHub (Sep 30, 2023):

Try https://github.com/fatedier/frp#server-manage-plugins

<!-- gh-comment-id:1741728158 --> @fatedier commented on GitHub (Sep 30, 2023): Try https://github.com/fatedier/frp#server-manage-plugins
Author
Owner

@github-actions[bot] commented on GitHub (Oct 31, 2023):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1786254122 --> @github-actions[bot] commented on GitHub (Oct 31, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2901
No description provided.