Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
documentation:latest:soapsessionbackend [2011/11/09 12:09]
127.0.0.1 external edit
documentation:latest:soapsessionbackend [2016/07/19 12:10]
127.0.0.1 external edit
Line 3: Line 3:
 LL::NG portal provides SOAP end points for sessions management: LL::NG portal provides SOAP end points for sessions management:
   * **sessions/​**:​ read only access to sessions (enough for distant Handlers)   * **sessions/​**:​ read only access to sessions (enough for distant Handlers)
-  * **adminSessions/​**:​ read/write access to sessions (required for distant Portal ​or distant Manager)+  * **adminSessions/​**:​ read/write access to sessions (required for distant Portaldistant Manager ​or distant Handlers which modify sessions)
  
 This session backend can be used to share sessions stored in a non-network backend (like [[filesessionbackend|file session backend]]) or in a network backend protected with a firewall that only accepts HTTP flows. This session backend can be used to share sessions stored in a non-network backend (like [[filesessionbackend|file session backend]]) or in a network backend protected with a firewall that only accepts HTTP flows.
Line 22: Line 22:
 ^  Name  ^  Comment ​ ^  Example ​ ^ ^  Name  ^  Comment ​ ^  Example ​ ^
 |  **proxy** ​ | URL of sessions SOAP end point | %%http://​auth.example.com/​index.pl/​sessions%% | |  **proxy** ​ | URL of sessions SOAP end point | %%http://​auth.example.com/​index.pl/​sessions%% |
 +
 +<note tip>Use /​adminSessions if the Handler need to modify the session, for example if you configured an idle timeout.</​note>​
  
 ==== Apache ==== ==== Apache ====