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
documentation:latest:redirections [2016/07/19 12:10]
127.0.0.1 external edit
documentation:latest:redirections [2019/01/15 15:54] (current)
Line 1: Line 1:
-====== ​Handler ​Redirections ======+====== Redirections ====== 
 + 
 +===== Handler Redirections ​=====
  
 <​note>​When a user access a Handler without a cookie, he is redirected on portal, and the target URL is encoded in redirection URL (to redirect user after authentication process).</​note>​ <​note>​When a user access a Handler without a cookie, he is redirected on portal, and the target URL is encoded in redirection URL (to redirect user after authentication process).</​note>​
  
-===== Protocol and port =====+==== Protocol and port ====
  
 To encode the redirection URL, the handler will use some Apache environment variables and also configuration settings: To encode the redirection URL, the handler will use some Apache environment variables and also configuration settings:
Line 11: Line 13:
 These parameters can be configured in Manager, in ''​General Parameters''​ > ''​Advanced parameters''​ > ''​Handler redirections''​. These parameters can be configured in Manager, in ''​General Parameters''​ > ''​Advanced parameters''​ > ''​Handler redirections''​.
  
-<note tip>​These settings can be overriden ​per virtual host, see [[configvhost|virtual host management]].</​note>​+<note tip>​These settings can be overridden ​per virtual host, see [[configvhost|virtual host management]].</​note>​
  
-===== Forbidden and Server error =====+==== Forbidden and Server error ====
  
 Handler use the default Apache error code for the following cases: Handler use the default Apache error code for the following cases:
Line 45: Line 47:
  
  
-====== Portal Redirections ​======+===== Portal Redirections =====
  
 <​note>​If a user is redirected from handler to portal for authentication and once he is authenticated,​ portal redirects him to the redirection URL.</​note>​ <​note>​If a user is redirected from handler to portal for authentication and once he is authenticated,​ portal redirects him to the redirection URL.</​note>​
Line 51: Line 53:
   * **Redirection message**: ​ The redirection from portal can be done either with code 303 (See Other), or with a JavaScript redirection. Often the redirection takes some time because it is user's first access to the protected app, so a new app session has to be created : JavaScript redirection improves user experience by informing that authentication is performed, and by preventing from clicking again on the button because it is too slow.   * **Redirection message**: ​ The redirection from portal can be done either with code 303 (See Other), or with a JavaScript redirection. Often the redirection takes some time because it is user's first access to the protected app, so a new app session has to be created : JavaScript redirection improves user experience by informing that authentication is performed, and by preventing from clicking again on the button because it is too slow.
   * **Keep redirections for Ajax**: By default, when an Ajax request is done on the portal for an unauthenticated user (after a redirection done by the handler), a 401 code will be sentwith a ''​WWW-Authenticate''​ header containing "SSO <​portal-URL>"​. Set this option to 1 to keep the old behavior (return of HTML code).   * **Keep redirections for Ajax**: By default, when an Ajax request is done on the portal for an unauthenticated user (after a redirection done by the handler), a 401 code will be sentwith a ''​WWW-Authenticate''​ header containing "SSO <​portal-URL>"​. Set this option to 1 to keep the old behavior (return of HTML code).
 +  * **Skip re-auth confirmation**:​ by default, when re-authentication is needed, a confirmation screen is displayed to let user accept the re-authentication. If you enable this option, user will be directly redirected to login page.