Merge pull request #72 from neilt/1.11

Update password text and add to index

part-administration.tex

@@ -127,7 +127,7 @@ \section{User creation}
 
 Enter the password to be used for this user into the ``Password'' field. If you're
 importing a user, please leave the field empty -- that will prevent the password
-from being changed.  Note that initial passwords (and password resets) are only 
+from being changed.  Note that initial passwords \index{password} (and password resets) are only 
 valid for one day unless the user logs in and changes his/her password.
 
 The ``Import'' field is discussed in \secref{sec-user-imports}. To create a new
@@ -185,15 +185,15 @@ \subsection{Editing user information and authorizations}
 Similarly, there may be reasons to change the user information, such as a last name
 (e.g. upon marriage).
 
-Note that if you reset a password, the new password is valid for one day unless
+Note that if you reset a password \index{password}, the new password is valid for one day unless
 changed.  The preferred business process is for the individual with permissions to reset
 the password, give the new password to the user, they then log in and
 immediately change it.
 
 \subsection{Changing user preferences}
 \label{subsec-user-management-user-prefs}
 
-Each user can change his preferences and password through the \texttt{Preferences}
+Each user can change his preferences \index{preferences} and password \index{password} through the \texttt{Preferences}
 top level menu. See \figref{fig:user-preferences}.
 
 \begin{figure}[h]
@@ -225,7 +225,7 @@ \section{User imports}
 able to use that user with the current company, it needs to be ``imported'' instead.
 
 The difference between creating a new user and importing one is that the ``Import''
-radio button should be set to ``Yes'' and that you should not fill out a password.
+radio button should be set to ``Yes'' and that you should not fill out a \index{password} password.
 If you do, the password of that user will be overwritten for all companies.
 
 All other fields are still applicable: the data entered for other companies isn't

part-configuration.tex

@@ -373,15 +373,17 @@ \subsubsection{Password duration}
 the user's \texttt{Preferences} screen. If this field is empty, passwords set through that method
 won't expire.
 
-A user will receive password expiration reminders upon logging starting a week before password
+The user has to log into LedgerSMB after this field is changed and prior to the expiration of the previous setting in order for the new duration to take effect.
+
+A user will receive password \index{password duration} expiration reminders upon logging starting a week before password
 expiry. When not acted upon, starting two days before expiry an hourly popup will appear
 requesting the user to change the password.
 
 The application behaves this way because users with expired passwords won't be able to log in:
 their password will need to be reset by a user admin.
 
 \begin{quote}
-Note that passwords set by admins for other users expire within 24 hours after setting them.
+Note that passwords set by admins for other users expire \index{password expiration} within 24 hours after setting them.
 This value is hard coded and can't be overruled. This is a security measure taken to make
 sure as few unused accounts as possible exist: Existence of such accounts could open up security
 holes.