mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #1416] [Feature Request] Token for client only or no token required for clients #1115
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#1115
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @scegg on GitHub (Aug 30, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1416
In case for publishing service through xtcp, server token need to be disclosed to all users which is not safe.
Please consider to add a token in common for client only, or ignore token check for xtcp client side users.
Thanks.
@fatedier commented on GitHub (Aug 30, 2019):
xtcp is not provided for different user now.
@scegg commented on GitHub (Aug 30, 2019):
Yes, currently, there is no user separate function on server. If the server has a token set in common block, all users who know this token on the same server will share all function.
The feature requested is: if some client is created only for accessing a specified xtcp service, through there is a key for each xtcp service already, why the token for the whole server is required in this client config?
@fatedier commented on GitHub (Aug 30, 2019):
Token is used to check if frpc have permission to login to frps.
I know your demand and it can't be satisfied now. It requires more time to redesign with a low priority. I will first do the server plugin feature.
@deadlineOvO commented on GitHub (Oct 4, 2019):
Try creating a new separate configuration?
@zhaoyc1990 commented on GitHub (Oct 25, 2019):
@scegg If you will use the golang development language, you can use the 'user' item under the configuration [common] of FRPC. Then modify FRPs to judge when FRPC logs in, so as to achieve the purpose.
@scegg commented on GitHub (Oct 25, 2019):
If I were able to use golang, there will be a pull request instead of this issue lol.
@fatedier commented on GitHub (Jan 5, 2020):
Since v0.31.0, you can implement this feature by server manage plugin.
And if you do that, you can share your plugin in https://github.com/gofrp/plugin (create an issue).