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. See Table 29-1.
Table 29-1 Impersonation JSP Files
|
File name |
Location |
Description |
|---|---|---|
|
https://NIDP-hostname:port/nidp/jsp/impersonator.jsp |
This file controls all impersonator actions, such as 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 help desk session. |
|
|
https://NIDP-hostname:port/nidp/jsp/impersonatee.jsp |
This file controls all impersonatee actions, such as seeing a help desk session request from an impersonator, approving or denying the request, and seeing whether a previously approved request is active. |
If you have built a custom user portal for your users, you must edit the impersonator.jsp file. For information about how to edit a file, see Modifying Configurations.
Make the change to the following default value (line 218):
window.parent.location = "/nidp/portal";
The change depends on whether the custom user portal loads as an iFrame or as a standalone web page.
iFrame: 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: Change the line as follows:
window.location="URL of the page that loads after an active impersonation session starts"