2020-05-14 23:29:41 +02:00
|
|
|
Apache
|
|
|
|
======
|
|
|
|
|
|
|
|
============== ===== ========
|
|
|
|
Authentication Users Password
|
|
|
|
============== ===== ========
|
2020-05-18 09:56:39 +02:00
|
|
|
✔
|
2020-05-14 23:29:41 +02:00
|
|
|
============== ===== ========
|
|
|
|
|
|
|
|
Presentation
|
|
|
|
------------
|
|
|
|
|
|
|
|
LL::NG can delegate authentication to Apache, so it is possible to use
|
|
|
|
any `Apache authentication
|
|
|
|
module <http://httpd.apache.org/docs/current/howto/auth.html>`__, for
|
|
|
|
example Kerberos, Radius, OTP, etc.
|
|
|
|
|
|
|
|
|
2020-05-21 15:13:24 +02:00
|
|
|
.. attention::
|
2020-05-14 23:29:41 +02:00
|
|
|
|
2020-06-06 23:50:34 +02:00
|
|
|
To authenticate users by using Kerberos, you can now use
|
2020-05-14 23:29:41 +02:00
|
|
|
the new :doc:`Kerberos authentication module<authkerberos>` which allow
|
2020-05-18 09:56:39 +02:00
|
|
|
one to chain Kerberos in a :doc:`combination<authcombination>`\
|
2020-05-14 23:29:41 +02:00
|
|
|
|
|
|
|
|
2020-05-18 09:56:39 +02:00
|
|
|
.. tip::
|
2020-05-14 23:29:41 +02:00
|
|
|
|
|
|
|
Apache authentication module will set the ``REMOTE_USER``
|
|
|
|
environment variable, which will be used by LL::NG to get authenticated
|
|
|
|
user.
|
|
|
|
|
|
|
|
Configuration
|
|
|
|
-------------
|
|
|
|
|
|
|
|
LL::NG
|
|
|
|
~~~~~~
|
|
|
|
|
|
|
|
In General Parameters > Authentication modules, choose ``Apache`` as
|
|
|
|
authentication backend.
|
|
|
|
|
|
|
|
You may want to failback to another authentication backend in case of
|
|
|
|
the Apache authentication fails. Use then the
|
|
|
|
:doc:`Multiple authentication module<authmulti>`, for example:
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
Apache;LDAP
|
|
|
|
|
|
|
|
|
2020-05-18 09:56:39 +02:00
|
|
|
.. tip::
|
2020-05-14 23:29:41 +02:00
|
|
|
|
|
|
|
In this case, the Apache authentication module should not
|
|
|
|
require a valid user and not be authoritative, else Apache server will
|
|
|
|
return an error and not let LL::NG Portal manage the failback
|
|
|
|
authentication.
|
|
|
|
|
|
|
|
.. _apache-1:
|
|
|
|
|
|
|
|
Apache
|
|
|
|
~~~~~~
|
|
|
|
|
|
|
|
The Apache configuration depends on the module you choose, you need to
|
|
|
|
look at the module documentation, for example:
|
|
|
|
|
|
|
|
- `Kerberos <http://modauthkerb.sourceforge.net/>`__
|
|
|
|
- `NTLM <http://search.cpan.org/~speeves/Apache2-AuthenNTLM-0.02/AuthenNTLM.pm>`__
|
|
|
|
- `Radius <http://freeradius.org/mod_auth_radius/>`__
|
|
|
|
- ...
|
|
|
|
|
|
|
|
Tips
|
|
|
|
----
|
|
|
|
|
|
|
|
Kerberos
|
|
|
|
~~~~~~~~
|
|
|
|
|
|
|
|
The Kerberos configuration is quite complex. You can find some
|
|
|
|
configuration tips :doc:`on this page<kerberos>`.
|
|
|
|
|
|
|
|
|
2020-05-18 09:56:39 +02:00
|
|
|
.. tip::
|
2020-05-14 23:29:41 +02:00
|
|
|
|
|
|
|
Prefer new :doc:`Kerberos<authkerberos>` module.
|
|
|
|
|
|
|
|
Compatibility with Identity Provider modules
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
When using IDP modules (like CAS or SAML), the activation of Apache
|
|
|
|
authentication can alter the operation. This is because the client often
|
|
|
|
need to request directly the IDP, and the Apache authentication will
|
|
|
|
block the request.
|
|
|
|
|
|
|
|
In this case, you can add in the Apache authentication module:
|
|
|
|
|
2020-05-21 15:13:24 +02:00
|
|
|
.. code-block:: apache
|
2020-05-14 23:29:41 +02:00
|
|
|
|
2020-05-18 09:56:39 +02:00
|
|
|
Satisfy any
|
|
|
|
Order allow,deny
|
2020-05-14 23:29:41 +02:00
|
|
|
allow from APPLICATIONS_IP
|
|
|
|
|
|
|
|
This will bypass the authentication module for request from
|
|
|
|
APPLICATIONS_IP.
|