metamod:security_plans

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
metamod:security_plans [2008-11-27 10:15:06]
heikok 		metamod:security_plans [2022-05-31 09:29:32] (current)
Line 45: Line 45:
   * Using tomcat within apache (mod_jk, mod_proxy), having same security realm. This would be a good solution for SSO on the http-side (simply having one application), but might require extra care when setting up protection for one data-catalog, which can be seen from apache as up to 3 (eventually more) http-pathes (opendap, http, WCS).   * Using tomcat within apache (mod_jk, mod_proxy), having same security realm. This would be a good solution for SSO on the http-side (simply having one application), but might require extra care when setting up protection for one data-catalog, which can be seen from apache as up to 3 (eventually more) http-pathes (opendap, http, WCS).
  
-==== Changes needed ====+===== Changes needed =====
  
-=== BasicAuth for /upl ===+==== BasicAuth for /upl ====
  
   * .htaccess protection for all /upl/* pages   * .htaccess protection for all /upl/* pages
Line 53: Line 53:
   * Only username known to metamod $_SERVER{REMOTE_USER} after login, not institution/working directory. This information should be stored in another place.   * Only username known to metamod $_SERVER{REMOTE_USER} after login, not institution/working directory. This information should be stored in another place.
  
-=== (Optional) upload-area per user ===+==== (Optional) upload-area per user ====
  
   * each user should have a user-directory, where he can upload files via ftp   * each user should have a user-directory, where he can upload files via ftp
  • metamod/security_plans.1227780906.txt.gz
  • Last modified: 2022-05-31 09:23:19
  • (external edit)