authentication, and the logout URL changes to match the assigned reverse proxy. For more
information on changing the authentication proxy, see
Authentication Proxy Service," on page
3 Redirect application logout requests to the AGLogout page.
4 Click OK.
The Access Gateway does not support the following logout pages that were used in previous version
of Access Manager and iChain:
/cmd/BM-Logout
/cmd/ICSLogout
2.10.2 Customizing the Access Gateway Logout Page
You can create your own logout page and configure the Access Gateway to use it. To do this, you
need to modify the
directory:
Linux:
/opt/novell/nesp/lib/webapp/jsp
Window:
\Program Files\Novell\Tomcat\webapp\nesp\jsp
You can modify the file to display what you want or you can modify it to redirect the user to your
custom page. The following sections provide some tips for accomplishing this task:
"Modifying the Header" on page 106
"Redirecting to Your Custom Page" on page 106
"Calling Different Logout Pages" on page 107
Modifying the Header
The
logoutSuccess.jsp
header of the logout page is controlled by the branding of the
how to modify
Access Manager 3.1 SP2 Identity Server
IMPORTANT: Save a copy of your modified
Gateway, you need to restore this file.
Redirecting to Your Custom Page
One way to provide redirection is to replace the information in the
logoutSuccess.jsp
<body>
<script language="JavaScript">
top.location.href='http://<hostname/path>';
</script>
</body>
Replace the <hostname/path> string with the location of your customized logout page.
106 Novell Access Manager 3.1 SP2 Access Gateway Guide
logoutSuccess.jsp
file is called in a frame from the
for logos, titles, and colors, see
nidp.jsp
file with something similar to the following:
Section 6.3.2, "Changing the
195.
file on the Access Gateway. It is located in the following
nidp.jsp
nidp.jsp
"Rebranding the
Guide.
file. Every time you upgrade your Access
nidp.jsp
file. The branding in the
file. For information on
Header" in the
Novell
element of the
<body>
Need help?
Do you have a question about the ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 and is the answer not in the manual?