Login-Credentials based redirection?
ajaygargnsit at gmail.com
Fri Apr 7 15:41:56 UTC 2017
I have been searching if it is possible to do a one-to-one mapping,
something like ::
Also, ports 9000, 9001 will be firewalled from the public.
Above will ensure that someone wanting to get access to say port 9000, will
have to come via http://18.104.22.168/9000. and must know the credentials
Do I make sense?
If yes, can someone please point me out as to how to specify
username:password on the URL basis.
Thanks and Regards,
On Fri, Apr 7, 2017 at 7:15 PM, Ajay Garg <ajaygargnsit at gmail.com> wrote:
> Hi All.
> We have setup multiple ssh-reverse tunnels, and our server will be
> listening to ports from 9000 to 10000.
> The server will have a public-IP, and we DO NOT want just anyone to look
> into any of the ports by trying ::
> http://22.214.171.124:9001 and so on ...
> So, we are wondering if we can do something like this ::
> 1. User types in a URL, let's say https://126.96.36.199/index.html
> 2. The user gets presented with a login/password page.
> 3. Depending upon the credentials passed, the user gets "proxied" to the
> appropriate end-url.
> So, a user with credentials for port 9000 will ONLY be able to see
> A user with credentials for port 9001 will ONLY be able to see
> http://188.8.131.52:9001, and so on ..
> An important point to note that the URLs http://184.108.40.206:9000,
> http://220.127.116.11:9001 must be not be directly accessible, else it defeats
> the purpose of authentication at first place.
> Is the above approach feasible logically and technically-via-nginx?
> Will be grateful for pointers.
> Thanks and Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx