department changes

This commit is contained in:
Roland Gruber 2017-03-04 11:18:30 +01:00
parent 4d6724430e
commit cb62f63cd8
2 changed files with 884 additions and 883 deletions

View File

@ -1,6 +1,7 @@
15.03.2017 5.7 15.03.2017 5.7
- 2-factor authentication for admin login and self service with privacyIDEA - 2-factor authentication for admin login and self service with privacyIDEA
- PDF files use DejaVu serif font for better readability and more supported characters (e.g. Cyrillic) - PDF files use DejaVu serif font for better readability and more supported characters (e.g. Cyrillic)
- Windows users: the department option now uses attribute "department" instead of "departmentNumber"
- Updated Debian dependencies - Updated Debian dependencies
- Fixed bugs: - Fixed bugs:
-> Comparison issue prevents saving of values (185) -> Comparison issue prevents saving of values (185)

View File

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="a_installation"> <chapter id="a_installation">
<title>Installation</title> <title>Installation</title>
<section id="a_install"> <section id="a_install">
@ -14,8 +14,8 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Apache/Nginx webserver (SSL recommended) with PHP module <para>Apache/Nginx webserver (SSL recommended) with PHP module (PHP
(PHP 5 (&gt;= 5.2.4) with ldap, gettext, xml, openssl and optional 5 (&gt;= 5.2.4) with ldap, gettext, xml, openssl and optional
mcrypt)</para> mcrypt)</para>
</listitem> </listitem>
@ -44,9 +44,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para>Internet Explorer 9 <emphasis <para>Internet Explorer 9 <emphasis role="bold">(compatibility
role="bold">(compatibility mode turned mode turned off)</emphasis></para>
off)</emphasis></para>
</listitem> </listitem>
<listitem> <listitem>
@ -95,8 +94,8 @@
automatically in testing and the stable releases. You can automatically in testing and the stable releases. You can
run<literal> </literal><para><emphasis role="bold">apt-get run<literal> </literal><para><emphasis role="bold">apt-get
install ldap-account-manager</emphasis></para>to install LAM install ldap-account-manager</emphasis></para>to install LAM
on your server. Additionally, you may download the latest on your server. Additionally, you may download the latest LAM
LAM Debian packages from the <ulink type="" Debian packages from the <ulink type=""
url="http://www.ldap-account-manager.org/">LAM url="http://www.ldap-account-manager.org/">LAM
homepage</ulink> or the <ulink homepage</ulink> or the <ulink
url="http://packages.debian.org/search?keywords=ldap-account-manager">Debian url="http://packages.debian.org/search?keywords=ldap-account-manager">Debian
@ -108,8 +107,8 @@
<para>dpkg -i ldap-account-manager_*.deb</para> <para>dpkg -i ldap-account-manager_*.deb</para>
<para>If you get any messages about missing <para>If you get any messages about missing dependencies
dependencies run now: apt-get -f install</para> run now: apt-get -f install</para>
</listitem> </listitem>
<listitem> <listitem>
@ -142,14 +141,13 @@
</imageobject> </imageobject>
</inlinemediaobject></entry> </inlinemediaobject></entry>
<entry>There are RPM packages available on the <ulink <entry>There are RPM packages available on the <ulink type=""
type="" url="http://www.ldap-account-manager.org/">LAM url="http://www.ldap-account-manager.org/">LAM
homepage</ulink>. The packages can be installed with these homepage</ulink>. The packages can be installed with these
commands:<para><emphasis role="bold">rpm -e commands:<para><emphasis role="bold">rpm -e
ldap-account-manager ldap-account-manager ldap-account-manager-lamdaemon</emphasis>
ldap-account-manager-lamdaemon</emphasis> (if an older (if an older version is installed)</para><para><emphasis
version is installed)</para><para><emphasis role="bold">rpm role="bold">rpm -i &lt;path to LAM
-i &lt;path to LAM
package&gt;</emphasis></para><literallayout> package&gt;</emphasis></para><literallayout>
</literallayout><para><emphasis role="bold">Note:</emphasis> The RPM packages </literallayout><para><emphasis role="bold">Note:</emphasis> The RPM packages
for Fedora/CentOS do not contain a dependency to PHP due to for Fedora/CentOS do not contain a dependency to PHP due to
@ -164,9 +162,9 @@
<section> <section>
<title>Other RPM based distributions</title> <title>Other RPM based distributions</title>
<para>The RPM packages for Suse/Fedora are very generic and should <para>The RPM packages for Suse/Fedora are very generic and should be
be installable on other RPM-based distributions, too. The Fedora installable on other RPM-based distributions, too. The Fedora packages
packages use apache:apache as file owner and the Suse ones use use apache:apache as file owner and the Suse ones use
wwwrun:www.</para> wwwrun:www.</para>
</section> </section>
@ -213,8 +211,8 @@
<section> <section>
<title>Manual copy</title> <title>Manual copy</title>
<para>Copy the files into the html-file scope of the web server. <para>Copy the files into the html-file scope of the web server. For
For example /apache/htdocs or /var/www/html.</para> example /apache/htdocs or /var/www/html.</para>
<para>Then set the appropriate file permissions inside the LAM <para>Then set the appropriate file permissions inside the LAM
directory:</para> directory:</para>
@ -248,8 +246,8 @@
<title>With configure script</title> <title>With configure script</title>
<para>Instead of manually copying files you can also use the <para>Instead of manually copying files you can also use the
included configure script to install LAM. Just run these commands included configure script to install LAM. Just run these commands in
in the extracted directory:</para> the extracted directory:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -275,8 +273,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para>--with-web-root=DIRECTORY DIRECTORY is the name where <para>--with-web-root=DIRECTORY DIRECTORY is the name where LAM
LAM should be installed (default /usr/local/lam)</para> should be installed (default /usr/local/lam)</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</section> </section>
@ -295,8 +293,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para>Select "Edit general settings" to setup global settings <para>Select "Edit general settings" to setup global settings and
and to change the <link linkend="a_configPasswords">master to change the <link linkend="a_configPasswords">master
configuration password</link> (default is "lam").</para> configuration password</link> (default is "lam").</para>
</listitem> </listitem>
@ -326,8 +324,8 @@
<para>memory_limit = 64M</para> <para>memory_limit = 64M</para>
<para>For large installations (&gt;10000 LDAP entries) you may need <para>For large installations (&gt;10000 LDAP entries) you may need to
to increase the memory limit to 256M.</para> increase the memory limit to 256M.</para>
<para>If you run PHP with activated <ulink <para>If you run PHP with activated <ulink
url="http://www.hardened-php.net/suhosin/index.html">Suhosin</ulink> url="http://www.hardened-php.net/suhosin/index.html">Suhosin</ulink>
@ -486,22 +484,21 @@
<section> <section>
<title>Upgrading LAM or migrate from LAM to LAM Pro</title> <title>Upgrading LAM or migrate from LAM to LAM Pro</title>
<para>Upgrading from LAM to LAM Pro is like installing a new LAM <para>Upgrading from LAM to LAM Pro is like installing a new LAM version.
version. Simply install the LAM Pro packages/tar.bz2 instead of the LAM Simply install the LAM Pro packages/tar.bz2 instead of the LAM
ones.</para> ones.</para>
<section> <section>
<title>Upgrade LAM</title> <title>Upgrade LAM</title>
<para><emphasis role="bold">Backup configuration <para><emphasis role="bold">Backup configuration files</emphasis></para>
files</emphasis></para>
<para>Configuration files need only to be backed up for .tar.bz2 <para>Configuration files need only to be backed up for .tar.bz2
installations. DEB/RPM installations do not require this step.</para> installations. DEB/RPM installations do not require this step.</para>
<para>LAM stores all configuration files in the "config" folder. <para>LAM stores all configuration files in the "config" folder. Please
Please backup the following files and copy them after the new version backup the following files and copy them after the new version is
is installed.</para> installed.</para>
<simplelist> <simplelist>
<member>config/*.conf</member> <member>config/*.conf</member>
@ -535,9 +532,8 @@
<para><emphasis role="bold">Install new LAM (Pro) <para><emphasis role="bold">Install new LAM (Pro)
version</emphasis></para> version</emphasis></para>
<para>Please <link linkend="a_install">install</link> the new LAM <para>Please <link linkend="a_install">install</link> the new LAM (Pro)
(Pro) release. Skip the part about setting up LAM configuration release. Skip the part about setting up LAM configuration files.</para>
files.</para>
<para><emphasis role="bold">Restore configuration <para><emphasis role="bold">Restore configuration
files</emphasis></para> files</emphasis></para>
@ -545,9 +541,9 @@
<para>RPM:</para> <para>RPM:</para>
<para>Please check if there are any files ending with ".rpmsave" in <para>Please check if there are any files ending with ".rpmsave" in
/var/lib/ldap-account-manager/config. In this case you need to /var/lib/ldap-account-manager/config. In this case you need to manually
manually remove the .rpmsave extension by overwriting the package remove the .rpmsave extension by overwriting the package file. E.g.
file. E.g. rename default.user.rpmsave to default.user.</para> rename default.user.rpmsave to default.user.</para>
<para>DEB:</para> <para>DEB:</para>
@ -555,11 +551,11 @@
<para>tar.bz2:</para> <para>tar.bz2:</para>
<para>Please restore your configuration files from the backup. Copy <para>Please restore your configuration files from the backup. Copy all
all files from the backup folder to the config folder in your LAM Pro files from the backup folder to the config folder in your LAM Pro
installation. Do not simply replace the folder because the new LAM installation. Do not simply replace the folder because the new LAM (Pro)
(Pro) release might include additional files in this folder. Overwrite release might include additional files in this folder. Overwrite any
any existing files with your backup files.</para> existing files with your backup files.</para>
<para><emphasis role="bold">Final steps</emphasis></para> <para><emphasis role="bold">Final steps</emphasis></para>
@ -574,22 +570,28 @@
<section id="a_versUpgrade"> <section id="a_versUpgrade">
<title>Version specific upgrade instructions</title> <title>Version specific upgrade instructions</title>
<para>You need to follow all steps from your current version to the new version. Unless explicitly noticed there is no need to install an intermediate release.</para> <para>You need to follow all steps from your current version to the new
version. Unless explicitly noticed there is no need to install an
intermediate release.</para>
<section> <section>
<title>5.6 -&gt; 5.7</title> <title>5.6 -&gt; 5.7</title>
<para>No special actions needed.</para> <para>Windows: The department attribute was changed from
"departmentNumber" to "department" to match Windows user manager. The
attribute "departmentNumber" is no more supported by the Windows
module. You will need to reactivate the department option in your
server profile on module settings tab.</para>
</section> </section>
<section> <section>
<title>5.5 -&gt; 5.6</title> <title>5.5 -&gt; 5.6</title>
<para>Mail routing: No longer added by default. Use profile editor <para>Mail routing: No longer added by default. Use profile editor to
to activate by default for new users/groups.</para> activate by default for new users/groups.</para>
<para>Personal/Unix/Windows: no more replacement of e.g. <para>Personal/Unix/Windows: no more replacement of e.g. $user/$group
$user/$group on user upload</para> on user upload</para>
</section> </section>
<section> <section>
@ -618,8 +620,7 @@
<title>4.9 -&gt; 5.0</title> <title>4.9 -&gt; 5.0</title>
<para>Samba 3: If you used logon hours then you need to set the <para>Samba 3: If you used logon hours then you need to set the
correct time zone on tab "Generel settings" in server correct time zone on tab "Generel settings" in server profile.</para>
profile.</para>
</section> </section>
<section> <section>
@ -632,9 +633,9 @@
<title>4.4 -&gt; 4.5</title> <title>4.4 -&gt; 4.5</title>
<para>LAM will no longer follow referrals by default. This is ok for <para>LAM will no longer follow referrals by default. This is ok for
most installations. If you use LDAP referrals please activate most installations. If you use LDAP referrals please activate referral
referral following for your server profile (tab General settings following for your server profile (tab General settings -&gt; Server
-&gt; Server settings -&gt; Advanced options).</para> settings -&gt; Advanced options).</para>
<para>The self service pages now have an own option for allowed IPs. <para>The self service pages now have an own option for allowed IPs.
If your LAM installation uses IP restrictions please update the LAM If your LAM installation uses IP restrictions please update the LAM
@ -642,21 +643,21 @@
<para>Password self reset (LAM Pro) allows to set a backup email <para>Password self reset (LAM Pro) allows to set a backup email
address. You need to <link address. You need to <link
linkend="passwordSelfResetSchema_update">update</link> the LDAP linkend="passwordSelfResetSchema_update">update</link> the LDAP schema
schema if you want to use this feature.</para> if you want to use this feature.</para>
</section> </section>
<section> <section>
<title>4.3 -&gt; 4.4</title> <title>4.3 -&gt; 4.4</title>
<para>Apache configuration: LAM supports Apache 2.2 and 2.4. This <para>Apache configuration: LAM supports Apache 2.2 and 2.4. This
requires that your Apache server has enabled the "version" module. requires that your Apache server has enabled the "version" module. For
For Debian and Fedora this is the default setup. The Suse RPM will Debian and Fedora this is the default setup. The Suse RPM will try to
try to enable the version module during installation.</para> enable the version module during installation.</para>
<para>Kolab: User accounts get the object class "mailrecipient" by <para>Kolab: User accounts get the object class "mailrecipient" by
default. You can change this behaviour in the module settings default. You can change this behaviour in the module settings section
section of your LAM server profile.</para> of your LAM server profile.</para>
<para>Windows: sAMAccountName is no longer set by default. Enable it <para>Windows: sAMAccountName is no longer set by default. Enable it
in server profile if needed. The possible domains for the user name in server profile if needed. The possible domains for the user name
@ -688,17 +689,17 @@
following shells by default: /bin/bash, /bin/csh, /bin/dash, following shells by default: /bin/bash, /bin/csh, /bin/dash,
/bin/false, /bin/ksh, /bin/sh.</para> /bin/false, /bin/ksh, /bin/sh.</para>
<para>Please update your server/self service profile if you would <para>Please update your server/self service profile if you would like
like to change the list of valid login shells.</para> to change the list of valid login shells.</para>
</section> </section>
<section> <section>
<title>3.9 -&gt; 4.0</title> <title>3.9 -&gt; 4.0</title>
<para>The account profiles and PDF structures are now separated by <para>The account profiles and PDF structures are now separated by
server profile. This means that if you edit e.g. an account profile server profile. This means that if you edit e.g. an account profile in
in server profile A then this change will not affect the account server profile A then this change will not affect the account profiles
profiles in server profile B.</para> in server profile B.</para>
<para>LAM will automatically migrate your existing files as soon as <para>LAM will automatically migrate your existing files as soon as
the login page is loaded.</para> the login page is loaded.</para>
@ -728,9 +729,9 @@
</listitem> </listitem>
<listitem> <listitem>
<para>Please rename all files "*.rpmsave" and remove the <para>Please rename all files "*.rpmsave" and remove the file
file extension ".rpmsave". E.g. "default.user.rpmsave" needs extension ".rpmsave". E.g. "default.user.rpmsave" needs to be
to be renamed to "default.user".</para> renamed to "default.user".</para>
</listitem> </listitem>
<listitem> <listitem>
@ -769,24 +770,23 @@
<section> <section>
<title>3.5.0 -&gt; 3.6</title> <title>3.5.0 -&gt; 3.6</title>
<para><emphasis role="bold">Debian users:</emphasis> LAM 3.6 <para><emphasis role="bold">Debian users:</emphasis> LAM 3.6 requires
requires to install FPDF 1.7. You can download the package <ulink to install FPDF 1.7. You can download the package <ulink
url="http://packages.debian.org/search?keywords=php-fpdf&amp;searchon=names&amp;suite=all&amp;section=all">here</ulink>. url="http://packages.debian.org/search?keywords=php-fpdf&amp;searchon=names&amp;suite=all&amp;section=all">here</ulink>.
If you use Debian Stable (Squeeze) please use the package from If you use Debian Stable (Squeeze) please use the package from Testing
Testing (Wheezy).</para> (Wheezy).</para>
</section> </section>
<section> <section>
<title>3.4.0 -&gt; 3.5.0</title> <title>3.4.0 -&gt; 3.5.0</title>
<para><emphasis role="bold">LAM Pro:</emphasis> The global <para><emphasis role="bold">LAM Pro:</emphasis> The global
config/passwordMailTemplate.txt is no longer supported. You can config/passwordMailTemplate.txt is no longer supported. You can setup
setup the mail settings now for each LAM server profile which the mail settings now for each LAM server profile which provides more
provides more flexibility.</para> flexibility.</para>
<para><emphasis role="bold">Suse/Fedora RPM <para><emphasis role="bold">Suse/Fedora RPM installations:</emphasis>
installations:</emphasis> LAM is now installed to LAM is now installed to /usr/share/ldap-account-manager and
/usr/share/ldap-account-manager and
/var/lib/ldap-account-manager.</para> /var/lib/ldap-account-manager.</para>
<para>Please note that configuration files are not migrated <para>Please note that configuration files are not migrated
@ -819,8 +819,8 @@
<title>3.0.0 -&gt; 3.1.0</title> <title>3.0.0 -&gt; 3.1.0</title>
<para>LAM supported to set a list of valid workstations on the <para>LAM supported to set a list of valid workstations on the
"Personal" page. This required to change the LDAP schema. Since "Personal" page. This required to change the LDAP schema. Since 3.1.0
3.1.0 this is replaced by the new "Hosts" module for users.</para> this is replaced by the new "Hosts" module for users.</para>
<para>Lamdaemon: The sudo entry needs to be changed to <para>Lamdaemon: The sudo entry needs to be changed to
".../lamdaemon.pl *".</para> ".../lamdaemon.pl *".</para>
@ -909,4 +909,4 @@
</listitem> </listitem>
</orderedlist> </orderedlist>
</section> </section>
</chapter> </chapter>