Access Manager uses two .jsp files that control how Impersonation functions. You can load these files as stand-alone web pages, or into an iFrame on an existing web page. The files are defined in the following table:
Table 28-1 Impersonation JSP Files
|
File name |
Location |
Description |
|---|---|---|
|
impersonator.jsp |
https://NIDP-hostname:port/nidp/jsp/impersonator.jsp |
The impersonator.jsp file controls all impersonator actions, including sending a help desk session request to the impersonatee, seeing the status of a help desk session request that has already been sent, canceling a help desk session request, and ending a current help desk session. |
|
impersonatee.jsp |
https://NIDP-hostname:port/nidp/jsp/impersonatee.jsp |
The imperonatee.jsp controls all impersonatee actions, including seeing a help session request from the impersonator, approving or denying the request, and seeing whether a previously approved request is active or has ended. |
If you have built a custom user portal for your users, there is an additional file you must edit. The file is located on Identity Server at /opt/novell/nids/lib/webapp/jsp/impersonator.jsp. You need to make a change to the default login page (line 218):
window.parent.location = "/nidp/portal";
You must make a different change depending on if the custom user portal loads as an iFrame or a stand-alone web page.
iFrame: You must change "/nidp/portal" to be the full URL of the page that loads when an active impersonation session starts. For example:
window.parent.local="URL of the page that loads after an active impersonation session starts"
Stand-alone web page: You must also change the line to:
window.location="URL of the page that loads after an active impersonation session starts"