To encode the redirection URL, the handler will use some Apache environment variables and also configuration settings:
These parameters can be configured in Manager, in General Parameters
> Advanced parameters
> Handler redirections
.
Handler use the default Apache error code for the following cases:
These errors can be catch trough Apache ErrorDocument
directive or Nginx error_page
directive, to redirect user on a specific page:
# Apache: Common error page and security parameters ErrorDocument 403 http://auth.example.com/?lmError=403 ErrorDocument 500 http://auth.example.com/?lmError=500 ErrorDocument 503 http://auth.example.com/?lmError=503
# Nginx: Common error page and security parameters error_page 403 http://auth.example.com/?lmError=403; error_page 500 http://auth.example.com/?lmError=500; error_page 503 http://auth.example.com/?lmError=503;
It is also possible to redirect the user without using ErrorDocument
: the Handler will not returnV 403, 500, 503 code, but code 302 (REDIRECT).
The user will be redirected on portal URL with error in the lmError
URL parameter.
These parameters can be configured in Manager, in General Parameters
> Advanced parameters
> Handler redirections
:
WWW-Authenticate
header containing “SSO <portal-URL>”. Set this option to 1 to keep the old behavior (return of HTML code).