2020-05-14 23:29:41 +02:00
|
|
|
Logout forward
|
|
|
|
|
==============
|
|
|
|
|
|
|
|
|
|
Presentation
|
|
|
|
|
------------
|
|
|
|
|
|
2021-04-02 23:57:30 +02:00
|
|
|
Even if LL:NG can catch logout URL through
|
2020-05-18 09:56:39 +02:00
|
|
|
:ref:`virtual host rules<rules>`, you can have the
|
2020-05-14 23:29:41 +02:00
|
|
|
need to forward a logout to other applications, to close their local
|
|
|
|
|
sessions.
|
|
|
|
|
|
|
|
|
|
LL::NG has a logout forward mechanism, that will add a step in logout
|
|
|
|
|
process, to send logout requests (indeed, GET requests on application
|
|
|
|
|
logout URL) inside hidden iframes.
|
|
|
|
|
|
|
|
|
|
|
2020-05-18 09:56:39 +02:00
|
|
|
.. tip::
|
2020-05-14 23:29:41 +02:00
|
|
|
|
|
|
|
|
The logout request will be sent even if the user did not use
|
|
|
|
|
the application.
|
|
|
|
|
|
|
|
|
|
Configuration
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
Go in Manager, ``General parameters`` » ``Advanced parameters`` »
|
|
|
|
|
``Logout forward`` and click on ``Add a key``, then fill:
|
|
|
|
|
|
|
|
|
|
- **Key**: application name
|
|
|
|
|
- **Value**: application logout URL
|
|
|
|
|
|
|
|
|
|
|
2020-05-21 15:13:24 +02:00
|
|
|
.. attention::
|
2020-05-14 23:29:41 +02:00
|
|
|
|
|
|
|
|
The request on logout URL will be sent after user is
|
|
|
|
|
disconnected, so you should unprotect this URL if it is protected by an
|
|
|
|
|
LL::NG Handler.
|
