[GH-ISSUE #2602] Is possible to configure different tokens for different clients?

gitea-mirror commented

2026-05-05 13:20:06 -06:00

Owner

Copy link

Originally created by @cassc on GitHub (Oct 5, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2602

Describe the feature request

Currently only one token can be configured in common section inside the frps configuration file.

Is possible to configure different tokens for different clients?

Describe alternatives you've considered

Running multple frps instance

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @cassc on GitHub (Oct 5, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2602 ### Describe the feature request Currently only one token can be configured in `common` section inside the frps configuration file. Is possible to configure different tokens for different clients? ### Describe alternatives you've considered Running multple frps instance ### 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:20:06 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:20:09 -06:00

Author

Owner

Copy link

@v20z commented on GitHub (Oct 31, 2021):

Here is "frp server plugin to support multiple users for frp"
https://github.com/gofrp/fp-multiuser

@v20z commented on GitHub (Oct 31, 2021): Here is "frp server plugin to support multiple users for frp" https://github.com/gofrp/fp-multiuser

gitea-mirror commented

2026-05-05 13:20:10 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 1, 2021):

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

@github-actions[bot] commented on GitHub (Dec 1, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified