37 lines
918 B
ReStructuredText
37 lines
918 B
ReStructuredText
|
Logout forward
|
||
|
|
==============
|
||
|
|
|
||
|
|
Presentation
|
||
|
|
------------
|
||
|
|
|
||
|
|
Even if LL:NG can catch logout URL trough
|
||
|
|
:doc:`virtual host rules<writingrulesand_headers>`, you can have the
|
||
|
|
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.
|
||
|
|
|
||
|
|
|
||
|
|
.. tip::
|
||
|
|
|
||
|
|
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
|
||
|
|
|
||
|
|
|
||
|
|
.. important::
|
||
|
|
|
||
|
|
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.
|