The EPISHIP Impersonation API enables administrators to securely assume the identity of other users within the system. You can develop tools that facilitate support troubleshooting, user verification, and administrative actions by temporarily acting as another user without requiring their credentials.
View Doc →
The following figure shows the relationship between your EPISHIP app, the EPISHIP API, and Impersonation services.
Figure 1. EPISHIP API relationship diagram. Impersonation session initiation and termination flow.
EPISHIP’s administrative interface leverages impersonation to allow support staff to “see what the user sees.” This capability is critical for diagnosing permission issues, validating user-specific configurations, and providing hands-on assistance.
The REST API that manages the lifecycle of an impersonation session. It handles the secure switching of user contexts and the restoration of the original administrator session upon completion.
Strictly controlled via Bearer tokens. Only users with specific administrative privileges can initiate impersonation requests. The system logs all actions taken during an impersonation session for security auditing.
A mechanism that temporarily overrides the current user’s identity with that of the target `userId`. This session remains active until an explicit “leave” command is issued, which redirects the administrator back to their original context.
Users can use the EPISHIP Impersonation API to perform common workflows, such as:
Impersonation properties and parameters available through the EPISHIP Impersonation API:
