navhome
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
navhome [2007/09/30 16:23] faltin |
navhome [2007/10/01 08:59] faltin |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| The NAV bar is always available, not only on the home page, as a navigating bar on the top. It provides buttons for login / logout, link to the toolbox, user-defined quicklinks, userinfo, and preferences. | The NAV bar is always available, not only on the home page, as a navigating bar on the top. It provides buttons for login / logout, link to the toolbox, user-defined quicklinks, userinfo, and preferences. | ||
| + | |||
| + | |||
| Line 48: | Line 50: | ||
| === Use LDAP === | === Use LDAP === | ||
| - | If you will have many NAV users, consider using LDAP. LDAP is configured in the ''webfront/webfront.conf''. Example of usage follows:... FIXME | + | If you will have many NAV users, consider using LDAP. LDAP is configured in the ''webfront/webfront.conf''. LDAP configuration |
| + | and usage [[ldapauthentication|is documented here]]. A brief explanation follows: | ||
| The way LDAP works with NAV is that if a user is not defined manually in the NAV user account base, NAV will use LDAP. The user will then be stored locally in addition, also with password information. Next time the user logs in, LDAP is still used for authentication, if the password is changed in LDAP, the local NAV user base will be updated. If LDAP one day does not respond, the NAV user will still get access to NAV with its local cached user name and password! We find this more robust, which is of utmost importance for a tool monitoring the network infrastructure (if the tool does not work when part of the network is down, we have a problem). | The way LDAP works with NAV is that if a user is not defined manually in the NAV user account base, NAV will use LDAP. The user will then be stored locally in addition, also with password information. Next time the user logs in, LDAP is still used for authentication, if the password is changed in LDAP, the local NAV user base will be updated. If LDAP one day does not respond, the NAV user will still get access to NAV with its local cached user name and password! We find this more robust, which is of utmost importance for a tool monitoring the network infrastructure (if the tool does not work when part of the network is down, we have a problem). | ||
| Line 56: | Line 59: | ||
| The toolbox lists all the NAV tools with a brief explaination and lets you navigate to your tool of interest. | The toolbox lists all the NAV tools with a brief explaination and lets you navigate to your tool of interest. | ||
| + | |||
| ==== Userinfo ==== | ==== Userinfo ==== | ||
| - | Userinfo displays information about you and lets you change your password. | + | Userinfo displays information about you: your username, name, organization and group memberships. Userinfo also lets you change your password. For "normal" users this is the place to change password, as they do not have access to the user admin panel. |
| Line 85: | Line 89: | ||
| If you have activated quicklink #1 and/or quicklink #2 using navigational preferences they will be visible from the NAV bar. | If you have activated quicklink #1 and/or quicklink #2 using navigational preferences they will be visible from the NAV bar. | ||
| + | |||
| Line 92: | Line 97: | ||
| the various welcome-files, edit your contact information and more. | the various welcome-files, edit your contact information and more. | ||
| - | If you would like to use LDAP or adjust the user inactivity timer, make changes in ''webfront.conf''. | + | If you would like to use [[ldapauthentication|LDAP]] or adjust the user inactivity timer, make changes in ''webfront.conf''. |
| ====== Log files ====== | ====== Log files ====== | ||
navhome.txt · Last modified: 2008/06/02 09:46 by morten
Page Tools
