Install guide

</FilesMatch>
2. Update wow.env:
prompt> vi $OWHOME/WebApps/conf/wow.env
and change SECURITY_LEVEL to B or C.
Protecting ‘Static’ Documents
The WOW security model is largely aimed at preventing access to dynamic pages created
on the fly in WOW. This section explains how to protect certain static documents, e.g. an
AssetJournal project, which requires selective security. The restricted dir list mechanism
described earlier in this section provides blanket protection for certain directories, but even
legitimate users cannot get to these directories.
One possibility is to set up a custom .htaccess and password file for the specified
directory. Apache will then authenticate all access to static files in that directory. Notes that
this will have no effect on WOW dynamic pages, e.g. Z MAP Plus browsing. To
implement:
1. Create a password file. Use the htpasswd utility to create a passwd file. The
example below creates a file called ajpasswd with user ‘tight’, passwd ‘aj2001’:
prompt> htpasswd –bc /etc/apache2/.ajpasswd tight aj2001
2. Create an .htaccess file. Create a file with contents as listed below:
AuthType basic
AuthName "Tight AJ Projects"
AuthUserFile "/etc/apache2/.ajpasswd"
Require valid-user
3. Copy .htaccess to the required directory. Place the file into all directories that
require the same security policy.
4. Configure Apache to recognize the .htaccess file:
prompt> vi /etc/httpd/conf/httpd.conf
Change AllowOverride from None to AuthConfig within the <Directory />
stanza.
5. Restart Apache:
prompt> /usr/sbin/apachectl restart
WOW 5000.0.1.11 Release Notes Page 25 of 104 March 2014