Commit 9041afec authored by Clément OUDOT's avatar Clément OUDOT

Doc update

parent 84520302
......@@ -66,5 +66,21 @@ This can be used to protect applications relying on <code>REMOTE_USER</code> env
&nbsp;
&lt;/<span class="kw3">VirtualHost</span>&gt;</pre>
<p>
<p><div class="notetip">
Sometimes, <acronym title="Hypertext Preprocessor">PHP</acronym> applications also check the <acronym title="Hypertext Preprocessor">PHP</acronym>_AUTH_USER and <acronym title="Hypertext Preprocessor">PHP</acronym>_AUHT_PW environment variables. You can set them the same way:
</p>
<pre class="code file apache"><span class="kw1">SetEnvIfNoCase</span> Auth-<span class="kw1">User</span> <span class="st0">&quot;(.*)&quot;</span> PHP_AUTH_USER=$1
<span class="kw1">SetEnvIfNoCase</span> Auth-Password <span class="st0">&quot;(.*)&quot;</span> PHP_AUTH_PW=$<span class="nu0">1</span></pre>
<p>
Of course, you need to <a href="../../documentation/1.0/passwordstore.html" class="wikilink1" title="documentation:1.0:passwordstore">store password in session</a> to fill <acronym title="Hypertext Preprocessor">PHP</acronym>_AUTH_PW.
</div></p>
</p>
</div>
</div><!-- closes <div class="dokuwiki export">-->
\ No newline at end of file
......@@ -65,4 +65,24 @@ Go in Manager, <code>General Parameters</code> » <code>Sessions </code> » <cod
</p>
</div>
<!-- SECTION "Configuration" [643-] --></div><!-- closes <div class="dokuwiki export">-->
\ No newline at end of file
<!-- SECTION "Configuration" [643-787] -->
<h2><a name="usage" id="usage">Usage</a></h2>
<div class="level2">
<p>
User password is now available in <code>$_password</code> variable. For example, to send it in an header:
</p>
<pre class="code">
Auth-Password =&gt; $_password
</pre>
<p>
<p><div class="notetip">For security reasons, the password is not shown in sessions explorer.
</div></p>
</p>
</div>
<!-- SECTION "Usage" [788-] --></div><!-- closes <div class="dokuwiki export">-->
\ No newline at end of file
......@@ -123,13 +123,13 @@ Remove the <code>-p</code> options if you want to delete old files.
<p>
<p><div class="noteimportant">
The migration of application list in ini file will work, but it will then be hard to update. You should use the Manager and reconfigure all <a href="../../documentation/1.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.0:portalmenu">categories and applications</a> trough it, and then comment <code>applicationList</code> in ini file.
</div></p>
<p><div class="notewarning">
Be sure that <code>lemonldap-ng.ini</code> is readable by your Apache server and not for other:
</p>
<ul>
<li class="level1"><div class="li"> The migration of application list in ini file will work, but it will then be hard to update. You should use the Manager and reconfigure all categories and applications trough it, and then comment application list in ini file.</div>
</li>
<li class="level1"><div class="li"> Be sure that lemonldap-ng.ini is readable by your Apache server and not for other:</div>
</li>
</ul>
<pre class="code shell">chmod 640 /etc/lemonldap-ng/lemonldap-ng.ini
chown root:www-data /etc/lemonldap-ng/lemonldap-ng.ini</pre>
......@@ -140,7 +140,25 @@ chown root:www-data /etc/lemonldap-ng/lemonldap-ng.ini</pre>
</p>
</div>
<!-- SECTION "LemonLDAP::NG configuration files" [777-2569] -->
<!-- SECTION "LemonLDAP::NG configuration files" [777-2634] -->
<h2><a name="custom_skin" id="custom_skin">Custom skin</a></h2>
<div class="level2">
<p>
If you have built a custom skin for <acronym title="LemonLDAP::NG">LL::NG</acronym> portal, you will need to adapt it to the new version.
</p>
<p>
If you just modified the <acronym title="Cascading Style Sheets">CSS</acronym> file, you can follow the <a href="../../documentation/1.0/portalcustom.html#skin_customization" class="wikilink1" title="documentation:1.0:portalcustom">skin customization documentation</a> and copy you <acronym title="Cascading Style Sheets">CSS</acronym> in the new skin.
</p>
<p>
If you modified also the templates, you have to import all templates changes into your skin. The easiest way is maybe to start by copying new skin and then import your changes into it.
</p>
</div>
<!-- SECTION "Custom skin" [2635-3102] -->
<h2><a name="customized_scripts_parameters" id="customized_scripts_parameters">Customized scripts parameters</a></h2>
<div class="level2">
......@@ -177,7 +195,7 @@ This will prevent your local modifications to be dropped when you will update yo
</p>
</div>
<!-- SECTION "Customized scripts parameters" [2570-3507] -->
<!-- SECTION "Customized scripts parameters" [3103-4040] -->
<h2><a name="liberty_alliance_portal" id="liberty_alliance_portal">Liberty Alliance portal</a></h2>
<div class="level2">
......@@ -191,7 +209,7 @@ To replace it, LemonLDAP::NG has now SAML2 authentication backend.
</p>
</div>
<!-- SECTION "Liberty Alliance portal" [3508-3697] -->
<!-- SECTION "Liberty Alliance portal" [4041-4230] -->
<h2><a name="dbi_configuration_backend" id="dbi_configuration_backend">DBI configuration backend</a></h2>
<div class="level2">
......@@ -214,4 +232,4 @@ To replace it, LemonLDAP::NG has now SAML2 authentication backend.
</p>
</div>
<!-- SECTION "DBI configuration backend" [3698-] --></div><!-- closes <div class="dokuwiki export">-->
\ No newline at end of file
<!-- SECTION "DBI configuration backend" [4231-] --></div><!-- closes <div class="dokuwiki export">-->
\ No newline at end of file
How to build RPM LemonLDAP::NG
== How to build RPM LemonLDAP::NG ==
%_topdir: where you build RPMs (by default, /usr/src/redhat)
- Install rpm-build package
- Install all build dependencies (see BuildRequires in lemonldap-ng.spec)
- Put lemonldap-ng.spec in %_topdir/SPECS
- Put LemonLDAP::NG tarball in %_topdir/SOURCES
- Put LemonLDAP::NG tarball in %_topdir/SOURCES (built with 'make dist')
- Edit ~/.rpmmacros and set your build parameters (example for RHEL5):
-----
%_topdir /home/user/build
......@@ -13,7 +12,20 @@ How to build RPM LemonLDAP::NG
%rhel 5
-----
- Go to %_topdir
- Do rpmbuild -ba SPECS/lemonldap-ng.spec
- Do rpmbuild -ta SOURCES/lemonldap-ng-VERSION.tar.gz
This RPM can be build for several distribution like RedHat, CentOS, Fedora, OpenSuSE...
This RPM can be built for several distribution like RedHat, CentOS, Fedora, OpenSuSE...
== Update YUM repository ==
The YUM repository is hosted on http://lemonldap-ng.org/rpm
First copy RPM files (they must be signed!) and source RPM:
$ scp *.noarch.rpm lemonldapng@lemonldap-ng.org:rpm/noarch/
$ scp *.src.rpm lemonldapng@lemonldap-ng.org:rpm/SRPMS/
Then connect on server and launch repodata:
$ ssh lemonldapng@lemonldap-ng.org
lemonldapng@lemonldap-ng.org$ repodata rpm/
That's all!
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment