Login as
To help troubleshoot issues on their website or support portal, administrators can log in as the user experiencing the problem using ReachFive.
You can log in as another user in the ReachFive Console if you have access to the Profiles page, or use the dedicated Login as API endpoint. If you wish to use the API, refer to the Login as via API section below.
Configure the Login as feature
To configure the Login as feature, follow the instructions below.
Prerequisites
You must whitelist the following URLs in your selected first-party identity API client:
-
The URL of your ReachFive account in the Allowed Origins (CORS) field (e.g.
https://brand.com). -
Authentication callback route URLs on your website in the Allowed Callback URLs field (e.g.
https://brand.com/logged-in,https://brand.com/signed-up).
Configuration
-
Sign in to your ReachFive Console.
-
Go to .
-
Select your first-party identity client from the dropdown menu.
-
Define the Redirect url and make sure it has been whitelisted within your client.
-
Select the type of credential to return:
-
code- Authorization Code flow -
token- Implicit flow
-
| Credentials are returned as a query string parameter when using the API. |
Log in as another user in the console
-
Navigate to the desired profile to log in as ().
-
Click .
You are now redirected to your website or app, as defined in the Redirect url field, as the selected user via ReachFive.
| When you log in as another user, this generates a login user event which is traceable in the Recent Activity panel of the impersonated user, just like a standard login. |
Log in as via API
Here is the call sequence to follow when implementing the Login as feature via the Management API:
-
POST /oauth/token
-
GET redirectUrl returned by the previous request.
| For the Authorization code flow only, use the POST /oauth/token Identity API endpoint. |