January 4th, 2013
Forward launched with support for password-protection. Each time you started a Forward, you could use the
--auth option to set a username and password that would be required to open the Forward URL in a web browser. This worked great for occasionally password-protecting your Forwards, but could become tedious if you did it everyday.
So, we’ve added a new feature to make it more convenient for our customers who use password protection frequently. If you log in to forwardhq.com and click Preferences, you’ll find a new option to “automatically password-protect my Forwards”. With it enabled, you can leave off the
--auth option when you start a Forward, and it’ll automatically use the username and password that you’ve set in Preferences.
If you’d like one of your Forwards to have a different username and password, you can still use the
--auth option, and your Forward will use the username and password you provide instead of the default. And if you’ve set a default, but still want to create some non-password-protected Forwards, just use the
--no-auth option when starting one.
Finally, many of our Business and Small Business customers work on secret projects for their clients. In those cases, it could be a big issue if a developer were to forget to password-protect their Forward and it leaked to the public. In order to prevent this, Business and Small Business customers will find a second option in Preferences to “require all Forwards to be password-protected”. Enabling this will make it so that all Forwards will require a username and password (either the default, or set with the
--auth option) to view them.