How to password protect the port?

[awesomelionel]

If this is served on a public ip on port 5555, how do we configure the port that is served, or password protect it with basic auth?

[andre]

@awesomelionel there's nothing built into scout_realtime right for password protection right now, but I understand the use case. If this is a common concern, I'll look at implementing. Of course, pull requests are welcome too!

[ghost]

I'm assuming with both nginx and apache you could proxy pass to localhost:5555, and set up basic authentication from there as a temporary work around.

[nielsen]

+1 to http basic at least

[lol768]

This is something I'd really like to see, too.

[jasonmit]

Extending what @gregf mentioned, here is a working configuration I threw together to support basic auth via nginx reverse proxy.

htpasswd -c /var/www/scoutwww/.htpasswd admin

configuration for nginx proxy (/etc/nginx/sites-available/default):

server {
        listen   80;

        root /usr/share/nginx/www;
        index index.html index.htm;

        # Make site accessible from http://localhost/
        server_name localhost;

        location / {
                proxy_pass http://localhost:5555;
                auth_basic "Restricted Remote";
                auth_basic_user_file /var/scoutwww/.htpasswd;
        }
}

[Oxicode]

+1

[leolelego]

I agreed, it can be great to juste have a little password step !

[CodeBrauer]

+1