When installing an on-premise API Monitoring Radar Agent (previously known as Runscope Radar Agent), you may encounter an "invalid username/password" error message.
This error is due to recent changes made to the authentication process. The Radar Agent now requires a Runscope API token in order to properly authenticate. You must initially run the agent program with this API token via the
--token argument, then save the agent's configuration to a file.
To create the required Runscope API token, follow these steps:
- Log into Runscope.
- Click your Runscope icon in the upper-right below your name, then select Personal Information.
- On the left side click Applications.
The https://www.runscope.com/applications page opens.
- Click Create Application. All fields are required.
- Provide any Name for the app (perhaps something like "Runscope Agent Token" so it reflects its purpose).
- Provide any Website URL and Callback URL. -- It can be completely imaginary, so long as it "looks like" a URL to satisfy the parser on that page.
Note: Normally this application creation process is used to set up an application for use with an OAuth flow with a third-party app, so that app can access Runscope. But in this case, you use it to generate a Runscope API token for general Runscope API usage, and the URLs are ignored.
- Click the Create Application button.
- On the next page, scroll down a bit and you'll see the Personal Access Token. This is a UUID that is your Runscope API token which you'll use with the agent.
Now that you have your token, launch your agent like this:
If you are on multiple Runscope "Teams", you will be prompted to choose which "Team" to associate the agent with. If you are on only one Team, no such prompt will occur.
You'll also have an option to save the Agent configuration to a file -- do this. On future runs of the Runscope agent, you'll pass it a parameter that indicates its configuration file:
/path/to/runscope-radar -f /path/to/radar.conf
Note that the agent configuration file contains various parameters, including the API token (which you provided) as well as a unique agent ID that was generated and the Team ID that the agent is associated with. You can read more about the agent and its options here:
That's it! You may execute your test as desired.