Would it be possible to have some sort of authentication for clients? I am thinking of using this for servers I manage to keep a service port open with my server. The only problem is I dont want just anyone to be able to connect. I would like to just have a passcode to be included on the client end to connect.
Is this possible with the current setup?
Would it be possible to have some sort of authentication for clients? I am thinking of using this for servers I manage to keep a service port open with my server. The only problem is I dont want just anyone to be able to connect. I would like to just have a passcode to be included on the client end to connect.
Is this possible with the current setup?
Your local server can just require http auth and that requirement will be proxied. There is no other authentication setup as tunnels are randomly generated and meant to be short lived for demo or code testing.
If on the other hand by client authentication you mean the localtunnel client connecting to a localtunnel server, then no. There is nothing in place for that but should be relatively trivial to add. I recommend reading this code (https://github.com/defunctzombie/localtunnel-server/blob/master/server.js#L173). It is where it would be reasonable to expect the localtunnel client to pass along a token or some other authentication scheme.
Your local server can just require http auth and that requirement will be proxied. There is no other authentication setup as tunnels are randomly generated and meant to be short lived for demo or code testing.
If on the other hand by client authentication you mean the localtunnel client connecting to a localtunnel server, then no. There is nothing in place for that but should be relatively trivial to add. I recommend reading this code (https://github.com/defunctzombie/localtunnel-server/blob/master/server.js#L173). It is where it would be reasonable to expect the localtunnel client to pass along a token or some other authentication scheme.
Requiring the client to authenticate with the server is what I was thinking. I will give that a try, I looked at it and it seems pretty simple. At least for my use I just need to pass a "Passkey" field. It really dosent even need to be unique. Thanks
Requiring the client to authenticate with the server is what I was thinking. I will give that a try, I looked at it and it seems pretty simple. At least for my use I just need to pass a "Passkey" field. It really dosent even need to be unique. Thanks
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.
Would it be possible to have some sort of authentication for clients? I am thinking of using this for servers I manage to keep a service port open with my server. The only problem is I dont want just anyone to be able to connect. I would like to just have a passcode to be included on the client end to connect.
Is this possible with the current setup?
Your local server can just require http auth and that requirement will be proxied. There is no other authentication setup as tunnels are randomly generated and meant to be short lived for demo or code testing.
If on the other hand by client authentication you mean the localtunnel client connecting to a localtunnel server, then no. There is nothing in place for that but should be relatively trivial to add. I recommend reading this code (https://github.com/defunctzombie/localtunnel-server/blob/master/server.js#L173). It is where it would be reasonable to expect the localtunnel client to pass along a token or some other authentication scheme.
Requiring the client to authenticate with the server is what I was thinking. I will give that a try, I looked at it and it seems pretty simple. At least for my use I just need to pass a "Passkey" field. It really dosent even need to be unique. Thanks
Seems out of scope for this module currently.