Difference between revisions of "Require Login"
| Line 17: | Line 17: | ||
* you can go to a [http://www.webmaster-toolkit.com/htaccess-generator.shtml public htaccess/htpasswd generator] and copy the contents of what the "And this is what your .htpasswd file should look like..." box has | * you can go to a [http://www.webmaster-toolkit.com/htaccess-generator.shtml public htaccess/htpasswd generator] and copy the contents of what the "And this is what your .htpasswd file should look like..." box has | ||
* or you can use the htpasswd command (first time with -c) | * or you can use the htpasswd command (first time with -c) | ||
| − | + | {{Code|htpasswd -c .htpasswd USERNAME}} | |
| − | The file should contain lines like this: USERNAME:3Ce3F4zRcVf42 | + | The file should contain lines like this: |
| + | {{Text|USERNAME:3Ce3F4zRcVf42}} | ||
The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root: | The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root: | ||
| − | + | {{Code|cp .htpasswd /var/hda/web-apps/htpasswd | |
| − | + | chmod 600 /var/hda/web-apps/htpasswd | |
| − | + | chown apache:apache /var/hda/web-apps/htpasswd}} | |
= If you have webmin installed = | = If you have webmin installed = | ||
Revision as of 02:50, 10 August 2011
|
Update Needed |
|---|---|
| The contents of this page have become outdated or irrelevant. Please consider updating it. |
We have a budding feature to require login to individual webapps.
Note - each app may have created a corresponding webapp. It's in this webapp that the Login Required may be selected.
If selected, this settings makes it such that the application will ask for a user name and a password.
Unfortunately this is no integrated yet with the rest of the user/password system already in place, so for now, it has to be done using htaccess controls.
We have decided to make these a global setting, i.e. the users and password are all the same to all the apps that require login.
How to do it
This requires that an htaccess file and an htpassword file be created in a place that it's accessible to the web server.
To create an htpasswd file containing the users and passwords
- you can go to a public htaccess/htpasswd generator and copy the contents of what the "And this is what your .htpasswd file should look like..." box has
- or you can use the htpasswd command (first time with -c)
| bash code |
|---|
htpasswd -c .htpasswd USERNAME
|
The file should contain lines like this:
| Text |
|---|
USERNAME:3Ce3F4zRcVf42
|
The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root:
| bash code |
|---|
cp .htpasswd /var/hda/web-apps/htpasswd chmod 600 /var/hda/web-apps/htpasswd chown apache:apache /var/hda/web-apps/htpasswd
|
If you have webmin installed
After logging into webmin select “Others” on the left-hand side, click on “Protected Web Directories” and then select “Add protection for a new directory”.
In “Directory path” browse to/or enter the path to the ‘html’ web directory you wish to protect, in “Authentication realm” enter something like for example “Authentication required” (this will show up on the popup login box) and then click on create.
Now you need to setup users to allow login by clicking on “Add a new user” in “Associated users and groups”, when users have been created you should be good to go.
Note: After you have completed this process using webmin you can then select "un-protect selected directory" and use the HDA-Dashboard to enable/disable password protection.
