Not getting passed the prompt from the web browser

Hi Everyone,

Having problems authenticating any user, I am installing nagios in Red Hat Enterprise Edition 9.0. I followed instructions but I got stucked on this part, I must be missing something. I did what it said on manual:

Setting Up Authenticated Users

Now that you’ve configured the web server to require authentication for access to the CGIs, you’ll need to configure users who can access the CGIs. This is done by using the htpasswd command supplied with Apache.

Running the following command will create a new file called htpasswd.users in the /usr/local/nagios/etc directory. It will also create an username/password entry for nagiosadmin. You will be asked to provide a password that will be used when nagiosadmin authenticates to the web server.

htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin

Continue adding more users until you’ve created an account for everyone you want to access the CGIs. Use the following command to add additional users, replacing with the actual username you want to add. Note that the -c option is not used, since you already created the initial file.

htpasswd /usr/local/nagios/etc/htpasswd.users

Okay, so you’re done with the first part of what needs to be done. If you point your web browser to your Nagios CGIs you should be asked for a username and password. If you have problems getting user authentication to work at this point, read your webserver documentation for more info.

Enabling Authentication/Authorization Functionality In The CGIs

The next thing you need to do is make sure that the CGIs are configured to use the authentication and authorization functionality in determining what information and/or commands users have access to. This is done be setting the use_authentication variable in the CGI configuration file to a non-zero value. Example:

use_authentication=1

Okay, you’re now done with setting up basic authentication/authorization functionality in the CGIs

Thanks for your help!

… and what’s the problem exactly? :stuck_out_tongue:
Edited Mon Jun 06 2005, 04:29AM ]

Hi there,

I cannot get my users authenticated, not getting pass from that point. I enter username ans password and doesnot go any further, login authentication screen pops up again and again if I cancel that screen, said: Access Forbidden.

Thanks your your help.

Paste your errors from /etc/httpd/logs/error_log
so we can see what apache thinks of you triing to login.

here is /etc/httpd/logs/error_log

[Mon Jun 06 01:06:32 2005] [notice] Digest: generating secret for digest authentication …
[Mon Jun 06 01:06:32 2005] [notice] Digest: done
[Mon Jun 06 01:06:33 2005] [notice] Apache/2.0.40 (Red Hat Linu:evil: configured – resuming normal operations
[Mon Jun 06 01:07:24 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:07:24 2005] [error] [client 127.0.0.1] user victor not found: /nagios/
[Mon Jun 06 01:07:27 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:07:27 2005] [error] [client 127.0.0.1] user victor not found: /nagios/
[Mon Jun 06 01:10:52 2005] [warn] child process 5331 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5332 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5333 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5334 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5335 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5336 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5337 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5338 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5331 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5332 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5333 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5334 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5335 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5336 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5337 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:52 2005] [warn] child process 5338 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:53 2005] [warn] child process 5336 still did not exit, sending a SIGTERM
[Mon Jun 06 01:10:59 2005] [notice] Digest: generating secret for digest authentication …
[Mon Jun 06 01:10:59 2005] [notice] Digest: done
[Mon Jun 06 01:11:00 2005] [notice] Apache/2.0.40 (Red Hat Linu:evil: configured – resuming normal operations
[Mon Jun 06 01:11:12 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:11:12 2005] [error] [client 127.0.0.1] user victor not found: /nagios/
[Mon Jun 06 01:11:17 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:11:17 2005] [error] [client 127.0.0.1] user nagiosadmin not found: /nagios/
[Mon Jun 06 01:11:48 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:11:48 2005] [error] [client 127.0.0.1] user not found: /nagios/
[Mon Jun 06 01:15:50 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:15:50 2005] [error] [client 127.0.0.1] user victor not found: /nagios/
[Mon Jun 06 01:17:02 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:17:02 2005] [error] [client 127.0.0.1] user victor not found: /nagios/
[Mon Jun 06 01:17:06 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:17:06 2005] [error] [client 127.0.0.1] user nagiosadmin not found: /nagios/
[Mon Jun 06 01:17:11 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:17:11 2005] [error] [client 127.0.0.1] user nagiosvictor not found: /nagios/
[Mon Jun 06 01:19:30 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:19:30 2005] [error] [client 127.0.0.1] user nagiosadmin not found: /nagios/
[Mon Jun 06 01:19:34 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:19:34 2005] [error] [client 127.0.0.1] user nagiosadmin not found: /nagios/
[Mon Jun 06 01:23:56 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:23:56 2005] [error] [client 127.0.0.1] user nagiosadmin not found: /nagios/
[Mon Jun 06 01:24:00 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:24:00 2005] [error] [client 127.0.0.1] user nagiosvictor not found: /nagios/
[Mon Jun 06 01:25:58 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:25:58 2005] [error] [client 127.0.0.1] user nagiosadmin not found: /nagios/cgi-bin/
[Mon Jun 06 01:26:02 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:26:02 2005] [error] [client 127.0.0.1] user nagiosvictor not found: /nagios/cgi-bin/
[Mon Jun 06 01:26:07 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users
[Mon Jun 06 01:26:07 2005] [error] [client 127.0.0.1] user victor not found: /nagios/cgi-bin/
[Mon Jun 06 01:42:15 2005] [error] [client 127.0.0.1] user nagios not found: /nagios/
[Mon Jun 06 01:42:19 2005] [error] [client 127.0.0.1] user nagios not found: /nagios/
[Mon Jun 06 01:42:24 2005] [error] [client 127.0.0.1] user nagiosadmin: authentication failure for “/nagios/”: Password Mismatch
[Mon Jun 06 01:42:28 2005] [error] [client 127.0.0.1] user nagiosadmin: authentication failure for “/nagios/”: Password Mismatch
[Mon Jun 06 18:42:59 2005] [error] [client 127.0.0.1] user root not found: /nagios/
[Mon Jun 06 18:43:06 2005] [error] [client 127.0.0.1] user nagiosadmin: authentication failure for “/nagios/”: Password Mismatch
[Mon Jun 06 18:44:14 2005] [error] [client 127.0.0.1] user nagios not found: /nagios/
[Mon Jun 06 18:44:45 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:44:50 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:45:18 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:45:21 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /var/www/html/
[Mon Jun 06 18:45:21 2005] [error] [client 127.0.0.1] File does not exist: /var/www/html/error
[Mon Jun 06 18:45:26 2005] [error] [client 127.0.0.1] File does not exist: /var/www/html/nagios
[Mon Jun 06 18:45:31 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:45:44 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:47:42 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:48:02 2005] [error] [client 127.0.0.1] user nagios not found: /nagios/
[Mon Jun 06 18:48:10 2005] [error] [client 127.0.0.1] user nagiosadmin: authentication failure for “/nagios/”: Password Mismatch
[Mon Jun 06 18:48:14 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share
[Mon Jun 06 18:52:39 2005] [error] [client 127.0.0.1] Directory index forbidden by rule: /usr/local/nagios/share

here is /etc/httpd/httpd.conf file

httpd.conf - configuration for the Apache web server

Generated automatically… if you edit manually, the changes will be lost

the next time you run “apacheconfig”.

Section 1: Global Environment

The directives in this section affect the overall operation of Apache,

such as the number of concurrent requests it can handle or where it

can find its configuration files.

Don’t give away too much information about all the subcomponents

we are running. Comment out this line if you don’t mind remote sites

finding out what major optional modules you are running

ServerTokens OS

ServerRoot: The top of the directory tree under which the server’s

configuration, error, and log files are kept.

NOTE! If you intend to place this on an NFS (or otherwise network)

mounted filesystem then please read the LockFile documentation

(available at URL:http://httpd.apache.org/docs-2.0/mod/core.html#lockfile);

you will save yourself a lot of trouble.

Do NOT add a slash at the end of the directory path.

ServerRoot “/etc/httpd”

ScoreBoardFile: File used to store internal server process information.

If unspecified (the default), the scoreboard will be stored in an

anonymous shared memory segment, and will be unavailable to third-party

applications.

If specified, ensure that no two invocations of Apache share the same

scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.

#ScoreBoardFile run/httpd.scoreboard

PidFile: The file in which the server should record its process

identification number when it starts.

PidFile “/var/run/httpd.pid”

Timeout: The number of seconds before receives and sends time out.

TimeOut 300

KeepAlive: Whether or not to allow persistent connections (more than

one request per connection). Set to “Off” to deactivate.

KeepAlive false

MaxKeepAliveRequests: The maximum number of requests to allow

during a persistent connection. Set to 0 to allow an unlimited amount.

We recommend you leave this number high, for maximum performance.

MaxKeepAliveRequests 100

KeepAliveTimeout: Number of seconds to wait for the next request from the

same client on the same connection.

KeepAliveTimeout 15

Server-Pool Size Regulation (MPM specific)

prefork MPM

StartServers: number of server processes to start

MinSpareServers: minimum number of server processes which are kept spare

MaxSpareServers: maximum number of server processes which are kept spare

MaxClients: maximum number of server processes allowed to start

MaxRequestsPerChild: maximum number of requests a server process serves

StartServers 8 MinSpareServers 5 MaxSpareServers 20 MaxClients 150 MaxRequestsPerChild 100

worker MPM

StartServers: initial number of server processes to start

MaxClients: maximum number of simultaneous client connections

MinSpareThreads: minimum number of worker threads which are kept spare

MaxSpareThreads: maximum number of worker threads which are kept spare

ThreadsPerChild: constant number of worker threads in each server process

MaxRequestsPerChild: maximum number of requests a server process serves

StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0

perchild MPM

NumServers: constant number of server processes

StartThreads: initial number of worker threads in each server process

MinSpareThreads: minimum number of worker threads which are kept spare

MaxSpareThreads: maximum number of worker threads which are kept spare

MaxThreadsPerChild: maximum number of worker threads in each server process

MaxRequestsPerChild: maximum number of connections per server process

NumServers 5 StartThreads 5 MinSpareThreads 5 MaxSpareThreads 10 MaxThreadsPerChild 20 MaxRequestsPerChild 0

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, in addition to the default. See also the

directive.

Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

#Listen 12.34.56.78:80
Listen *:80

Load config files from the config directory “/etc/httpd/conf.d”.

Include conf.d/*.conf

Dynamic Shared Object (DSO) Support

To be able to use the functionality of a module which was built as a DSO you

have to place corresponding `LoadModule’ lines at this location so the

directives contained in it are actually available before they are used.

Statically compiled modules (those listed by `httpd -l’) do not need

to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so

LoadModule access_module modules/mod_access.so
LoadModule auth_module modules/mod_auth.so
LoadModule auth_anon_module modules/mod_auth_anon.so
LoadModule auth_dbm_module modules/mod_auth_dbm.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imap_module modules/mod_imap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so

ExtendedStatus controls whether Apache will generate “full” status

information (ExtendedStatus On) or just basic information (ExtendedStatus

Off) when the “server-status” handler is called. The default is Off.

#ExtendedStatus On

Section 2: ‘Main’ server configuration

The directives in this section set up the values used by the ‘main’

server, which responds to any requests that aren’t handled by a

definition. These values also provide defaults for

any containers you may define later in the file.

All of these directives may appear inside containers,

in which case these default settings will be overridden for the

virtual host being defined.

If you wish httpd to run as a different user or group, you must run

httpd as root initially and it will switch.

User/Group: The name (or #number) of the user/group to run httpd as.

. On SCO (ODT 3) use “User nouser” and “Group nogroup”.

. On HPUX you may not be able to use shared memory as nobody, and the

suggested workaround is to create a user www and use that user.

NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)

when the value of (unsigned)Group is above 60000;

don’t use Group #-1 on these systems!

User apache
Group apache

ServerAdmin: Your address, where problems with the server should be

e-mailed. This address appears on some server-generated pages, such

as error documents. e.g. [email protected]

ServerAdmin root@localhost

ServerName gives the name and port that the server uses to identify itself.

This can often be determined automatically, but we recommend you specify

it explicitly to prevent problems during startup.

If this is not set to valid DNS name for your host, server-generated

redirections will not work. See also the UseCanonicalName directive.

If your host doesn’t have a registered DNS name, enter its IP address here.

You will have to access it by its address anyway, and this will make

redirections work in a sensible way.

ServerName nagiosred

UseCanonicalName: Determines how Apache constructs self-referencing

URLs and the SERVER_NAME and SERVER_PORT variables.

When set “Off”, Apache will use the Hostname and Port supplied

by the client. When set “On”, Apache will use the value of the

ServerName directive.

UseCanonicalName on

DocumentRoot: The directory out of which you will serve your

documents. By default, all requests are taken from this directory, but

symbolic links and aliases may be used to point to other locations.

DocumentRoot “/var/www/html”

Disable autoindex for the root directory, and present a

default Welcome page if no other index page is present.

<LocationMatch “^/$”>
Options -Indexes
ErrorDocument 403 /error/noindex.html

UserDir: The name of the directory that is appended onto a user’s home

directory if a ~user request is received.

The path to the end user account ‘public_html’ directory must be

accessible to the webserver userid. This usually means that ~userid

must have permissions of 711, ~userid/public_html must have permissions

of 755, and documents contained therein must be world-readable.

Otherwise, the client will only receive a “403 Forbidden” message.

See also: httpd.apache.org/docs/misc/FAQ.html#forbidden

# # UserDir is disabled by default since it can confirm the presence # of a username on the system (depending on home directory # permissions). # UserDir "disable"
#
# To enable requests to /~user/ to serve the user's public_html
# directory, use this directive instead of "UserDir disable":
# 
#UserDir public_html

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

The index.html.var file (a type-map) is used to deliver content-

negotiated documents. The MultiViews Option can be used for the

same purpose, but it is much slower.

DirectoryIndex

AccessFileName: The name of the file to look for in each directory

for access control information. See also the AllowOverride directive.

AccessFileName .htaccess

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

<Files ~ “^.ht”>
Order allow,deny
Deny from all

TypesConfig describes where the mime.types file (or equivalent) is

to be found.

TypesConfig “/etc/mime.types”

DefaultType is the default MIME type the server will use for a document

if it cannot otherwise determine one, such as from filename extensions.

If your server contains mostly text or HTML documents, “text/plain” is

a good value. If most of your content is binary, such as applications

or images, you may want to use “application/octet-stream” instead to

keep browsers from trying to display binary files as though they are

text.

DefaultType text/plain

The mod_mime_magic module allows the server to use various hints from the

contents of the file itself to determine its type. The MIMEMagicFile

directive tells the module where the hint definitions are located.

# MIMEMagicFile /usr/share/magic.mime MIMEMagicFile conf/magic

HostnameLookups: Log the names of clients or just their IP addresses

e.g., www.apache.org (on) or 204.62.129.132 (off).

The default is off because it’d be overall better for the net if people

had to knowingly turn this feature on, since enabling it means that

each client request will result in AT LEAST one lookup request to the

nameserver.

HostNameLookups Off

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a

container, error messages relating to that virtual host will be

logged here. If you do define an error logfile for a

container, that host’s errors will be logged there and not here.

ErrorLog “/var/log/httpd/error_log”

LogLevel: Control the number of messages logged to the error_log.

Possible values include: debug, info, notice, warn, error, crit,

alert, emerg.

LogLevel warn

The following directives define some format nicknames for use with

a CustomLog directive (see below).

LogFormat “%h %l %u %t “%r” %>s %b “%{Referer}i” “%{User-Agent}i”” combined
LogFormat “%h %l %u %t “%r” %>s %b” common
LogFormat “%{Referer}i -> %U” referer
LogFormat “%{User-agent}i” agent

The location and format of the access logfile (Common Logfile Format).

If you do not define any access logfiles within a

container, they will be logged here. Contrariwise, if you do

define per- access logfiles, transactions will be

logged therein and not in this file.

CustomLog logs/access_log common

CustomLog logs/access_log combined

If you would like to have agent and referer logfiles, uncomment the

following directives.

#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent

If you prefer a single logfile with access, agent, and referer information

(Combined Logfile Format) you can use the following directive.

#CustomLog logs/access_log combined

Optionally add a line containing the server version and virtual host

name to server-generated pages (error documents, FTP directory listings,

mod_status and mod_info output etc., but not CGI generated documents).

Set to “EMail” to also include a mailto: link to the ServerAdmin.

Set to one of: On | Off | EMail

ServerSignature on

Aliases: Add here as many aliases as you need (with no limit). The format is

Alias fakename realname

Note that if you include a trailing / on fakename then the server will

require it to be present in the URL. So “/icons” isn’t aliased in this

example, only “/icons/”. If the fakename is slash-terminated, then the

realname must also be slash terminated, and if the fakename omits the

trailing slash, the realname must also omit it.

We include the /icons/ alias for FancyIndexed directory listings. If you

do not use FancyIndexing, you may comment this out.

Alias /icons/ “/var/www/icons/”

This should be changed to the ServerRoot/manual/. The alias provides

the manual, even if you choose to move your DocumentRoot. You may comment

this out if you do not care for the documentation.

Alias /manual “/var/www/manual”

# Location of the WebDAV lock database. DAVLockDB /var/lib/dav/lockdb

ScriptAlias: This controls which directories contain server scripts.

ScriptAliases are essentially the same as Aliases, except that

documents in the realname directory are treated as applications and

run by the server when requested rather than as documents sent to the client.

The same rules about trailing “/” apply to ScriptAlias directives as to

Alias.

ScriptAlias /nagios/cgi-bin “/usr/local/nagios/sbin”
<Directory “/usr/local/nagios/sbin”>

SSLRequireSSL

Options ExecCGI
AllowOverride AuthConfig
Order allow,deny
Allow from all

Order deny,allow

Deny from all

Allow from 127.0.0.1

# # Additional to mod_cgid.c settings, mod_cgid has Scriptsock # for setting UNIX socket for communicating with cgid. # #Scriptsock logs/cgisock

Redirect allows you to tell clients about documents which used to exist in

your server’s namespace, but do not anymore. This allows you to tell the

clients where to look for the relocated document.

Example:

Redirect permanent /foo example.com/bar

Directives controlling the display of server-generated directory listings.

FancyIndexing is whether you want fancy directory indexing or standard.

VersionSort is whether files containing version numbers should be

compared in the natural way, so that `apache-1.3.9.tar’ is placed before

`apache-1.3.12.tar’.

IndexOptions FancyIndexing VersionSort NameWidth=*

AddIcon* directives tell the server which icon to show for different

files or filename extensions. These are only displayed for

FancyIndexed directories.

AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif …
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

DefaultIcon is which icon to show for files which do not have an icon

explicitly set.

DefaultIcon /icons/unknown.gif

AddDescription allows you to place a short description after a file in

server-generated indexes. These are only displayed for FancyIndexed

directories.

Format: AddDescription “description” filename

#AddDescription “GZIP compressed document” .gz
#AddDescription “tar archive” .tar
#AddDescription “GZIP compressed tar archive” .tgz

ReadmeName is the name of the README file the server will look for by

default, and append to directory listings.

HeaderName is the name of a file which should be prepended to

directory indexes.

ReadmeName README.html
HeaderName HEADER.html

IndexIgnore is a set of filenames which directory indexing should ignore

and not include in the listing. Shell-style wildcarding is permitted.

IndexIgnore .??* ~ # HEADER README RCS CVS *,v *,t

AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress

information on the fly. Note: Not all browsers support this.

Despite the name similarity, the following Add* directives have nothing

to do with the FancyIndexing customization directives above.

AddEncoding x-compress Z
AddEncoding x-gzip gz tgz

DefaultLanguage and AddLanguage allows you to specify the language of

a document. You can then use content negotiation to give a browser a

file in a language the user can understand.

Specify a default language. This means that all data

going out without a specific language tag (see below) will

be marked with this one. You probably do NOT want to set

this unless you are sure it is correct for all cases.

* It is generally better to not mark a page as

* being a certain language than marking it with the wrong

* language!

DefaultLanguage nl

Note 1: The suffix does not have to be the same as the language

keyword — those with documents in Polish (whose net-standard

language code is pl) may wish to use “AddLanguage pl .po” to

avoid the ambiguity with the common suffix for perl scripts.

Note 2: The example entries below illustrate that in some cases

the two character ‘Language’ abbreviation is not identical to

the two character ‘Country’ code for its country,

E.g. ‘Danmark/dk’ versus ‘Danish/da’.

Note 3: In the case of ‘ltz’ we violate the RFC by using a three char

specifier. There is ‘work in progress’ to fix this and get

the reference data for rfc1766 cleaned up.

Danish (da) - Dutch (nl) - English (en) - Estonian (et)

French (fr) - German (de) - Greek-Modern (el)

Italian (it) - Norwegian (no) - Norwegian Nynorsk (nn) - Korean (kr)

Portugese (pt) - Luxembourgeois* (ltz)

Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cz)

Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)

Russian (ru) - Croatian (hr)

AddLanguage da .dk
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .et
AddLanguage fr .fr
AddLanguage de .de
AddLanguage he .he
AddLanguage el .el
AddLanguage it .it
AddLanguage ja .ja
AddLanguage pl .po
AddLanguage kr .kr
AddLanguage pt .pt
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pt-br .pt-br
AddLanguage ltz .ltz
AddLanguage ca .ca
AddLanguage es .es
AddLanguage sv .se
AddLanguage cz .cz
AddLanguage ru .ru
AddLanguage tw .tw
AddLanguage zh-tw .tw
AddLanguage hr .hr

LanguagePriority allows you to give precedence to some languages

in case of a tie during content negotiation.

Just list the languages in decreasing order of preference. We have

more or less alphabetized them here. You probably want to change this.

LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ltz ca es sv tw

ForceLanguagePriority allows you to serve a result page rather than

MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)

[in case no accepted languages matched the available variants]

ForceLanguagePriority Prefer Fallback

Specify a default charset for all pages sent out. This is

always a good idea and opens the door for future internationalisation

of your web site, should you ever want it. Specifying it as

a default does little harm; as the standard dictates that a page

is in iso-8859-1 (latin1) unless specified otherwise i.e. you

are merely stating the obvious. There are also some security

reasons in browsers, related to javascript and URL parsing

which encourage you to always set a default char set.

AddDefaultCharset ISO-8859-1

Commonly used filename extensions to character sets. You probably

want to avoid clashes with the language extensions, unless you

are good at carefully testing your setup after each change.

See ftp://ftp.isi.edu/in-notes/iana/assignm … acter-sets for

the official list of charset names and their respective RFCs

AddCharset ISO-8859-1 .iso8859-1 .latin1
AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen
AddCharset ISO-8859-3 .iso8859-3 .latin3
AddCharset ISO-8859-4 .iso8859-4 .latin4
AddCharset ISO-8859-5 .iso8859-5 .latin5 .cyr .iso-ru
AddCharset ISO-8859-6 .iso8859-6 .latin6 .arb
AddCharset ISO-8859-7 .iso8859-7 .latin7 .grk
AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb
AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5 .Big5 .big5

For russian, more than one charset is used (depends on client, mostly):

AddCharset WINDOWS-1251 .cp-1251 .win-1251
AddCharset CP866 .cp866
AddCharset KOI8-r .koi8-r .koi8-ru
AddCharset KOI8-ru .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8 .utf8

The set below does not map to a specific (iso) standard

but works on a fairly wide range of browsers. Note that

capitalization actually matters (it should not, but it

does for some browsers).

See ftp://ftp.isi.edu/in-notes/iana/assignm … acter-sets

for a list of sorts. But browsers support few.

AddCharset GB2312 .gb2312 .gb
AddCharset utf-7 .utf7
AddCharset utf-8 .utf8
AddCharset big5 .big5 .b5
AddCharset EUC-TW .euc-tw
AddCharset EUC-JP .euc-jp
AddCharset EUC-KR .euc-kr
AddCharset shift_jis .sjis

AddType allows you to add to or override the MIME configuration

file mime.types for specific file types.

AddType application/x-tar .tgz

AddHandler allows you to map certain file extensions to “handlers”:

actions unrelated to filetype. These can be either built into the server

or added with the Action directive (see below)

To use CGI scripts outside of ScriptAliased directories:

(You will also need to add “ExecCGI” to the “Options” directive.)

#AddHandler cgi-script .cgi

For files that include their own HTTP headers:

#AddHandler send-as-is asis

For server-parsed imagemap files:

AddHandler imap-file map

For type maps (negotiated resources):

(This is enabled by default to allow the Apache “It Worked” page

to be distributed in multiple languages.)

AddHandler type-map var

Filters allow you to process content before it is sent to the client.

To parse .shtml files for server-side includes (SSI):

(You will also need to add “Includes” to the “Options” directive.)

AddOutputFilter INCLUDES .shtml

Action lets you define media types that will execute a script whenever

a matching file is called. This eliminates the need for repeated URL

pathnames for oft-used CGI file processors.

Format: Action media/type /cgi-script/location

Format: Action handler-name /cgi-script/location

Customizable error responses come in three flavors:

1) plain text 2) local redirects 3) external redirects

Some examples:

#ErrorDocument 500 “The server made a boo boo.”
#ErrorDocument 404 /missing.html
#ErrorDocument 404 “/cgi-bin/missing_handler.pl”
#ErrorDocument 402 example.com/subscription_info.html

Alias /nagios/ “/usr/local/nagios/share”
<Directory “/usr/local/nagios/share”>

SSLRequireSSL

Options None
AllowOverride AuthConfig
Order allow,deny
Allow from all

Order deny,allow

Deny from all

Allow from 127.0.0.1

The following directives modify normal HTTP response behavior to

handle known problems with browser implementations.

BrowserMatch “Mozilla/2” nokeepalive
BrowserMatch “MSIE 4.0b2;” nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch “RealPlayer 4.0” force-response-1.0
BrowserMatch “Java/1.0” force-response-1.0
BrowserMatch “JDK/1.0” force-response-1.0

The following directive disables redirects on non-GET requests for

a directory that does not include the trailing slash. This fixes a

problem with Microsoft WebFolders which does not appropriately handle

redirects for folders with DAV methods.

BrowserMatch “Microsoft Data Access Internet Publishing Provider” redirect-carefully
BrowserMatch “^WebDrive” redirect-carefully

Allow server status reports, with the URL of servername/server-status

Change the “.your-domain.com” to match your domain to enable.

#<Location /server-status>

SetHandler server-status

Order deny,allow

Deny from all

Allow from .your-domain.com

#

Allow remote server configuration reports, with the URL of

servername/server-info (requires that mod_info.c be loaded).

Change the “.your-domain.com” to match your domain to enable.

#<Location /server-info>

SetHandler server-info

Order deny,allow

Deny from all

Allow from .your-domain.com

#

Proxy Server directives. Uncomment the following lines to

enable the proxy server:

#
#ProxyRequests On

#<Proxy *>

Order deny,allow

Deny from all

Allow from .your-domain.com

#

Enable/disable the handling of HTTP/1.1 “Via:” headers.

(“Full” adds the server version; “Block” removes all outgoing Via: headers)

Set to one of: Off | On | Full | Block

#ProxyVia On

To enable the cache as well, edit and uncomment the following lines:

(no cacheing without CacheRoot)

#CacheRoot “/etc/httpd/proxy”
#CacheSize 5
#CacheGcInterval 4
#CacheMaxExpire 24
#CacheLastModifiedFactor 0.1
#CacheDefaultExpire 1
#NoCache a-domain.com another-domain.edu joes.garage-sale.com

#

End of proxy directives.

Section 3: Virtual Hosts

VirtualHost: If you want to maintain multiple domains/hostnames on your

machine you can setup VirtualHost containers for them. Most configurations

use only name-based virtual hosts so the server doesn’t need to worry about

IP addresses. This is indicated by the asterisks in the directives below.

Please see the documentation at

URL:http://httpd.apache.org/docs-2.0/vhosts/

for further details before you try to setup virtual hosts.

You may use the command line option ‘-S’ to verify your virtual host

configuration.

Use name-based virtual hosting.

Where do we put the lock and pif files?

LockFile "/var/lock/httpd.lock"
CoreDumpDirectory “/etc/httpd”

Defaults for virtual hosts

Logs

Virtual hosts

Virtual host Default Virtual Host

<VirtualHost *>

ServerSignature email

DirectoryIndex  index.php index.html index.htm index.shtml 






LogLevel  warn
HostNameLookups off

Each directory to which Apache has access can be configured with respect

to which services and features are allowed and/or disabled in that

directory (and its subdirectories).

Note that from this point forward you must specifically allow

particular features to be enabled - so if something’s not working as

you might expect, make sure that you have specifically enabled it

below.

<Directory “/”>
Options FollowSymLinks

    AllowOverride None

<Directory “/var/www/html”>
Options Indexes Includes FollowSymLinks

    AllowOverride None
    Allow from from all

    
    Order allow,deny

<Directory “/var/www/icons”>
Options Indexes MultiViews

    AllowOverride None
    Allow from from all

    
    Order allow,deny

<Directory “/var/www/cgi-bin”>
Options ExecCGI

    AllowOverride None
    Allow from from all

    
    Order allow,deny

do you confirm the file /usr/local/nagios/etc/htpasswd.users exists?

Luca

Yes, it is there.

Vick

Is my httpp.conf configured properly? and Why I can’t authenticate?

vick try changing user and group of httpd.conf then restart httpd. you r logs shows that the browser can access the httpaswd

Mon Jun 06 01:07:24 2005] [error] [client 127.0.0.1] (13)Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users

and that user victor does not exist…

[Mon Jun 06 01:07:27 2005] [error] [client 127.0.0.1] user victor not found: /nagios/

you can also try to adduser a victor. then add victor to group nagios. then define group as nagios in httpd.conf.

oh dont forget to restart httpd

well good luck =)

I did that, but that user victor was not set up for accessing nagios, I was testing only what error message I get if I enter a different user. The user I am working on is nagios. I added recently victor; these users are showing when I open /usr/local/nagios/etc/htpassword.users.

thanks for your suggestion Graemann but still not working.

Vick

Thanks anyway guys, but I FOUND MY PROBLEM, my web authentication is working. The problem was File Owner permissions in htpasswd.users ; nagios user did not have access to open htpasswd.users, that’s why I could not get my user nagios or any other user web access to nagios site. So if you are new and having same problem, double check your file permissions under the user that is going to be running nagios and also make that user belong to Apache group.

Gook Luck everyone! :slight_smile:

Vick

Permission denied: Could not open password file: /usr/local/nagios/etc/htpasswd.users

Apache can’t read that file. Fix that problem, and all should be good.
Paste the output of this:
ls -la /usr/local/nagios
and also
ls -la /usr/local/nagios/etc

I found and fix my problem before. I gave owner permission to my user nagios, and after that my web authentication start working. thanks for your suggestion but I already fix that before your post.

Vick

try changing the user apache and group apach in httpd.conf to user nagios group nagios. assuming USER:nagios GROUP:nagios have the right permissions to htpasswd file.

sorry i guess my reply is delayed hehe. nice work. grats