Changes

Jump to navigation Jump to search
1,374 bytes removed ,  02:07, 10 November 2014
deleted section - moved
Line 16: Line 16:     
Various examples are shown in this article, which include how to implement secure authorised access to folders/subfolders in your SME Server ibays.  The default settings in SME Server allow you to secure the ibays using the Information Bay panel in server manager, by creating an ibay password which is used to allow authorised access to the ibay from the Internet, but this does not control access to individual folders.
 
Various examples are shown in this article, which include how to implement secure authorised access to folders/subfolders in your SME Server ibays.  The default settings in SME Server allow you to secure the ibays using the Information Bay panel in server manager, by creating an ibay password which is used to allow authorised access to the ibay from the Internet, but this does not control access to individual folders.
  −
===Enabling .htaccess on SME server===
  −
  −
These instructions are added here for general interest. Users should heed recommendations in this article & instead use custom templates where possible to achieve the same end result.
  −
  −
The alternative commonly used method of implementing access controls or custom directives on a Linux-based server is to create a file called .htaccess in the directory you want to control, and include your instructions in that file.
  −
  −
To allow users to independently change web access controls (where this is permitted by the system administrator), .htaccess can be enabled for an ibay using the following commands:
  −
  −
db accounts setprop ibayname AllowOverride All
  −
expand-template /etc/httpd/conf/httpd.conf
  −
service httpd-e-smith restart
  −
  −
The screen will display
  −
  −
Restarting httpd-e-smith                                  [  OK  ]
  −
  −
AllowOverride can be set to values other than "All", and should be set as narrowly as possible to meet users' needs.  Consult the [http://httpd.apache.org/docs/current/mod/core.html#allowoverride Apache documentation] for valid values of this parameter.  This is only required if there is a legitimate need for system users to independently change web access controls.  If this is enabled, the system administrator should regularly monitor the contents of .htaccess files to ensure security is not compromised.
  −
      
===Using custom templates to configure htaccess requirements===
 
===Using custom templates to configure htaccess requirements===
624

edits

Navigation menu