Module: nagvis Branch: master Commit: da948348281737ab00f8dbe1fff510e02dd4627b URL: http://nagvis.git.sourceforge.net/git/gitweb.cgi?p=nagvis/nagvis;a=commit;h=da948348281737ab00f8dbe1fff510e02dd4627b
Author: LaMi <[email protected]> Date: Tue Feb 16 22:09:57 2010 +0100 Updated documentation with new LogonMixed module --- docs/en_US/auth.html | 12 +++++++++--- docs/en_US/auth_old_style.html | 23 +++++++++++++++++++---- 2 files changed, 28 insertions(+), 7 deletions(-) diff --git a/docs/en_US/auth.html b/docs/en_US/auth.html index fd95b53..98eecec 100644 --- a/docs/en_US/auth.html +++ b/docs/en_US/auth.html @@ -11,9 +11,15 @@ <h2>Modularity</h2> <p>The AA has been splitted up in three module bases: LogonDialogs, Authentication, Autorization. All modules can be changed without affecting the others.</p> <h2>Default Modules</h2> -<p>By default NagVis uses a HTML form for logging on users and a SQLite database for storing users, passwords and permissions. Therefor it uses the HTML logon dialog (FrontendModLogonDialog), the SQLite authentication (CoreAuthModSQLite) and the SQLite autorization (CoreAuthorisationModSQLite) modules.</p> +<p>By default NagVis uses a mixed logon information request mode for logging on users and a SQLite + database for storing users, passwords and permissions. Therefor NagVis uses the LogonMixed module + which uses LogonEnv and LogonDialog in the background. The LogonMixed module tries to gather the + logon user name from the webserver environment. This means NagVis trusts the webserver authentication + if one is used. And if there is none it displays the LogonDialog for interactive login using the + HTML logon dialog.</p> <h2>Other Modules</h2> -<p>On delivery there are only the above authentication and autorisation modules available. Having such a modular structure it should be easy to create LDAP, MySQL, file based authentication and autorisation mechanism. By default NagVis uses the HTML logon dialog for requesting authentication informations from the user. It is possible to add own logon modules for serving other dialogs or ways of logging in.</p> -<p>It is also possible to realize a "trusted" authentication mechanism. NagVis uses the configured environment variable to identify the user. This way the user is not really authenticated with NagVis. NagVis trusts the provided username blindly. You can add several authentication mechanism to your webserver, started from the basic authentication used by Nagios (.htaccess) to single sign on environments. Simply set logonmodule to "LogonEnv", put the environment variable to use as username to the option logonenvvar and tell the authentication module to create users in the database when provided users does not exist.</p> +<p>On delivery there are only the above authentication and autorisation modules available. Having + such a modular structure it should be easy to create LDAP, MySQL, file based authentication and + autorisation mechanism.</p> </body> </html> diff --git a/docs/en_US/auth_old_style.html b/docs/en_US/auth_old_style.html index 2daa3f1..dac4815 100644 --- a/docs/en_US/auth_old_style.html +++ b/docs/en_US/auth_old_style.html @@ -6,12 +6,27 @@ </head> <body> <h1>Old Style Authentication</h1> -<p>In the versions prior to 1.5 NagVis didn't care much about the authentication and autorization. In the most environments NagVis used the basic authentication provided by Nagios. This was a side effect of that NagVis was placed in the <code>nagios/share</code> directory. -<p>In NagVis 1.5 the default installation directory has been moved to an own base directory. With this step a new Authentication and Autorization mechanism has been created. The main focus on this concept is to be modular and flexible.</p> -<p>If you really like to use the basic authentication provided by Nagios you may use the LogonEnv module to set up a trusted authentication. To make this possible simply set the following options in the <code>[global]</code> section in the NagVis main configuration file:</p> +<p>In the versions prior to 1.5 NagVis didn't care much about the authentication + and autorization. In the most environments NagVis used the basic authentication + provided by Nagios. This was a side effect of that NagVis was placed in the +<code>nagios/share</code> directory.</p> +<p>In NagVis 1.5 the default installation directory has been moved to an own + base directory. With this step a new Authentication and Autorization mechanism + has been created. The main focus on this concept is to be modular and flexible.</p> +<p>If you really like to use the basic authentication provided by Nagios you may + use the LogonMixed (default) or LogonEnv module to set up a trusted + authentication. The only difference is that the LogonMixed falls back to the HTML + form LogonDialog when no user is given by the webserver while LogonEnv simply + shows an access denied message.</p> +<p>To make this possible simply set the following options in the + <code>[global]</code> section in the NagVis main configuration file:</p> <pre>logonmodule="LogonEnv" logonenvvar="REMOTE_USER" logonenvcreateuser="1"</pre> -These lines tell NagVis to use the LogonEnv module which reads the authenticated user from an environment variable. The second parameter tells the LogonEnv module which variable to use for reading the users name. The third option tells the LogonEnv module to create unknown users in the NagVis AA database. +<p>These lines tell NagVis to use the LogonEnv module which reads the + authenticated user from an environment variable. The second parameter tells + the LogonEnv module which variable to use for reading the users name. + The third option tells the LogonEnv module to create unknown users in the + NagVis AA database.</p> </body> </html> ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Nagvis-checkins mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagvis-checkins
