Set up password protected web pages - Revision history

Kanabek at 13:56, 20 February 2009

2009-02-20T13:56:27Z

← Older revision		Revision as of 07:56, 20 February 2009
Line 1:		Line 1:
			==Using the Web Directory Access Control tool==

			The [https://members.swcp.com/webdiracl/ Web Directory Access Control tool] is a powerful, yet easy to use, method of password protecting a web page.

			Instructions are available at here, at the [[Web Directory Access Control]] tool page.



			==Using .htaccess==
			''This method is somewhat more complicated.''
	===Password protected web pages===		===Password protected web pages===
	Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.		Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.

Jamii: /* Password protected web pages */

2008-05-29T23:44:21Z

Password protected web pages

← Older revision		Revision as of 17:44, 29 May 2008
Line 13:		Line 13:
	</Limit>		</Limit>

	If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.		''If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.''

	3) Create a file in your home directory called .htgroup with the contents		3) Create a file in your home directory called .htgroup with the contents

Jamii: /* Password protected web pages */

2008-05-29T23:38:28Z

Password protected web pages

← Older revision		Revision as of 17:38, 29 May 2008
Line 19:		Line 19:
	my-users: pumpkin peanuts almonds walnuts		my-users: pumpkin peanuts almonds walnuts

	These are the users who are allowed to access. They will also need to have passwords defined in .htpasswd. To create this file and add the first username use the following UNIX command:		These are the users who are allowed to access. They will also need to have passwords defined in .htpasswd. To create this file and add the first username use the following UNIX command:

	htpasswd -c /users/login-name/.htpasswd username		htpasswd -c /users/login-name/.htpasswd username

	After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:		After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:

	htpasswd /users/login-name/.htpasswd username		htpasswd /users/login-name/.htpasswd username

Jamii: /* Password protected web pages */

2008-05-29T23:37:59Z

Password protected web pages

← Older revision		Revision as of 17:37, 29 May 2008
Line 22:		Line 22:

	htpasswd -c /users/login-name/.htpasswd username		htpasswd -c /users/login-name/.htpasswd username

	After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:		After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:

Jamii: /* Password protected web pages */

2008-05-29T23:37:43Z

Password protected web pages

← Older revision		Revision as of 17:37, 29 May 2008
Line 24:		Line 24:

	After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:		After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:

	htpasswd /users/login-name/.htpasswd username		htpasswd /users/login-name/.htpasswd username

	4) Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.		4) Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.

	chmod a+r /users/login-name/.htpasswd		chmod a+r /users/login-name/.htpasswd
	chmod a+r /users/login-name/.htgroup		chmod a+r /users/login-name/.htgroup

Jamii: /* Password protected web pages */

2008-05-29T23:37:12Z

Password protected web pages

← Older revision		Revision as of 17:37, 29 May 2008
Line 2:		Line 2:
	Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.		Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.

	#Create a new directory under your public_html directory which will store the protected pages.		1) Create a new directory under your public_html directory which will store the protected pages.
	#Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)		2) Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)

	AuthUserFile /users/login-name/.htpasswd		AuthUserFile /users/login-name/.htpasswd
Line 15:		Line 15:
	If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.		If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.

	#Create a file in your home directory called .htgroup with the contents		3) Create a file in your home directory called .htgroup with the contents

	my-users: pumpkin peanuts almonds walnuts		my-users: pumpkin peanuts almonds walnuts
Line 27:		Line 27:
	htpasswd /users/login-name/.htpasswd username		htpasswd /users/login-name/.htpasswd username

	#Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.		4) Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.

	chmod a+r /users/login-name/.htpasswd		chmod a+r /users/login-name/.htpasswd

Jamii: /* Password protected web pages */

2008-05-29T23:36:42Z

Password protected web pages

← Older revision		Revision as of 17:36, 29 May 2008
Line 2:		Line 2:
	Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.		Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.

	* Create a new directory under your public_html directory which will store the protected pages.		#Create a new directory under your public_html directory which will store the protected pages.
	* Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)		#Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)

	AuthUserFile /users/login-name/.htpasswd		AuthUserFile /users/login-name/.htpasswd
Line 15:		Line 15:
	If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.		If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.

	* Create a file in your home directory called .htgroup with the contents		#Create a file in your home directory called .htgroup with the contents

	my-users: pumpkin peanuts almonds walnuts		my-users: pumpkin peanuts almonds walnuts
Line 27:		Line 27:
	htpasswd /users/login-name/.htpasswd username		htpasswd /users/login-name/.htpasswd username

	* Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.		#Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.

	chmod a+r /users/login-name/.htpasswd		chmod a+r /users/login-name/.htpasswd

Jamii at 23:35, 29 May 2008

2008-05-29T23:35:53Z

Jamii: New page: Password protected web pages NCSA compatible web servers and modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. T...

2008-05-29T23:34:34Z

New page: Password protected web pages NCSA compatible web servers and modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. T...

New page

Password protected web pages
NCSA compatible web servers and modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.

* Create a new directory under your public_html directory which will store the protected pages.
* Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)

AuthUserFile /users/login-name/.htpasswd
AuthGroupFile /users/login-name/.htgroup
AuthName "password dialogue"
AuthType Basic
<Limit GET>
require group my-users
</Limit>

If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.

* Create a file in your home directory called .htgroup with the contents

my-users: pumpkin peanuts almonds walnuts

These are the users who are allowed to access. They will also need to have passwords defined in .htpasswd. To create this file and add the first username use the following UNIX command:

htpasswd -c /users/login-name/.htpasswd username

After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:

htpasswd /users/login-name/.htpasswd username

* Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.

chmod a+r /users/login-name/.htpasswd
chmod a+r /users/login-name/.htgroup
chmod a+r /users/login-name/public_html/somedir/.htaccess

While very useful, there are a couple of drawbacks to this htpasswd mechanism. Users and their passwords have to be created using the command line utility, and then manually entered into .htgroup. Also, each time you run the htpasswd utility, it sets the mode of the file .htpasswd back to 600. So it will have to manually changed back to mode 644 (chmod a+r). Users who want to automate this procedure via CGI should keep these things in mind for their scripting.

More detailed info is available at http://hoohoo.ncsa.uiuc.edu/docs/tutorials/user.html

← Older revision		Revision as of 17:35, 29 May 2008
Line 1:		Line 1:
	Password protected web pages		===Password protected web pages===
	~~NCSA compatible web servers and modern~~ web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.		Modern web browsers have the ability to perform password authentication. These passwords are independent of system passwords. To set up password protected web pages, follow these steps.

	* Create a new directory under your public_html directory which will store the protected pages.		* Create a new directory under your public_html directory which will store the protected pages.
	* Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)		* Create a file in that directory called .htaccess with the following contents (password dialogue is the text which will appear to the browser in the password dialogue window, and login-name is your SWCP login)

	AuthUserFile /users/login-name/.htpasswd		AuthUserFile /users/login-name/.htpasswd
	AuthGroupFile /users/login-name/.htgroup		AuthGroupFile /users/login-name/.htgroup
Line 12:		Line 12:
	require group my-users		require group my-users
	</Limit>		</Limit>

	If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.		If your website is on our older web server (kumo) please remove the quotes from the AuthName argument.

	* Create a file in your home directory called .htgroup with the contents		* Create a file in your home directory called .htgroup with the contents

	my-users: pumpkin peanuts almonds walnuts		my-users: pumpkin peanuts almonds walnuts

	These are the users who are allowed to access. They will also need to have passwords defined in .htpasswd. To create this file and add the first username use the following UNIX command:		These are the users who are allowed to access. They will also need to have passwords defined in .htpasswd. To create this file and add the first username use the following UNIX command:

	htpasswd -c /users/login-name/.htpasswd username		htpasswd -c /users/login-name/.htpasswd username

	After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:		After running the htpasswd command, you will be prompted for the users password twice. This will create a file /users/login-name/.htpasswd containing a encrypted form of the password. The -c option to the htpasswd command creates the password file so after adding the initial username use the following Unix command to add additional usernames:

	htpasswd /users/login-name/.htpasswd username		htpasswd /users/login-name/.htpasswd username

	* Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.		* Finally, all 3 files have to be world readable (chmod a+r). Now, when any files in password protected directory are accessed, the browser will get a password required dialogue.

	chmod a+r /users/login-name/.htpasswd		chmod a+r /users/login-name/.htpasswd
	chmod a+r /users/login-name/.htgroup		chmod a+r /users/login-name/.htgroup
	chmod a+r /users/login-name/public_html/somedir/.htaccess		chmod a+r /users/login-name/public_html/somedir/.htaccess

	While very useful, there are a couple of drawbacks to this htpasswd mechanism. Users and their passwords have to be created using the command line utility, and then manually entered into .htgroup. Also, each time you run the htpasswd utility, it sets the mode of the file .htpasswd back to 600. So it will have to manually changed back to mode 644 (chmod a+r). Users who want to automate this procedure via CGI should keep these things in mind for their scripting.		While very useful, there are a couple of drawbacks to this htpasswd mechanism. Users and their passwords have to be created using the command line utility, and then manually entered into .htgroup. Also, each time you run the htpasswd utility, it sets the mode of the file .htpasswd back to 600. So it will have to manually changed back to mode 644 (chmod a+r). Users who want to automate this procedure via CGI should keep these things in mind for their scripting.

	More detailed info is available at http://hoohoo.ncsa.uiuc.edu/docs/tutorials/user.html		More detailed info is available at http://hoohoo.ncsa.uiuc.edu/docs/tutorials/user.html