Changes

From Amahi Wiki
Jump to: navigation, search
16 bytes removed ,  20:59, 10 August 2011
no edit summary
== How to do it ==
*This requires creation of two files (.htaccess and htpassword) be placed in the directory of each web application you want to protect.
 
*The <code>htpasswd</code> file will identify user names/passwords (encrypted) and the <code>.htaccess</code> file will contain the code needed to use that file to protect the web application.
#First you need to identify the web application you want to protect and it's physical location (<code>/var/hda/web-app/appname</code>) on your server. For example, the path for '''Linfo''' would be <u>'''/var/hda/web-app/linfo'''</u>.
#Next, you need to decide on the user names/passwords who will have access. This has to be the HDA users credentials that are used to log into the HDA Dashboard.
* First you need to identify There are two options for creating the web application you want to protect and it's physical location (<code>htpasswd</var/hda/web-app/appnamecode> and </code>) on your server. For example, the path for '''Linfo''' would be htaccess<u/code>'''files:Navigate to [http:/var/hdawww.webmaster-toolkit.com/webhtaccess-app/linfo'''</u>generator* Next, you need to decide on the user names/passwords who will have accessshtml . This has to be the HDA users credentials that are used to log into the HDA Dashboardhtaccess Generator].
*There are two options for creating the <code>htpasswd</code> and <code>.htaccess</code> files:*#Navigate to [http://www.webmaster-toolkit.com/htaccess-generator.shtml .htaccess Generator].*#**#Use the htpasswd command:*#*{{Code|htpasswd -c .htpasswd USERNAME}}
12,424

edits