Store secure credentials for scripted browsers and API tests

You can use secure credentials with synthetic monitoring to store critical information, such as passwords, API keys, usernames, etc. This prevents scripted monitor users from viewing, updating, or deleting these values unless they have explicit permissions in New Relic. The credentials are securely stored using AES-GCM 256-bit encryption at rest with keys managed by Amazon AWS Key Management Service (KMS).

You can set secure credentials in New Relic One or with the API.

Requirements and limits

Before using secure credentials, review these requirements and guidelines:

Add or update secure credentials

You can add or update secure credentials using the UI or the Synthetics REST API.

To add, view, edit, or delete a secure credential for a scripted browser or API test monitor from the UI:

1. Go to one.newrelic.com > Synthetics > Secure credentials.
2. To add a new secure credential, look for the Create secure credential + button. If you have credentials already added, this button is at the top right.
   • Tips for creating the Key: choose a username or other meaningful key name to identify the secure credential. Use alphanumeric or underscore _ characters. Key names must be UPPERCASE.
   • Tips for creating the Value: Use any combination of alphanumeric or special characters. 10000 characters maximum. This field is not accessible via the API.
3. To edit an existing credential, click the ellipsis icon for options.
4. Associate the secure credential with a scripted browser or API test by editing the script.

After you add the secure credential to the script, the Secure credentials UI shows how many scripted monitors use that credential. This number is approximate and only updates after a monitor with a secure credential has actually been run.

Update the script

When using the Synthetics UI editor to create scripted browsers or API test monitors, follow these guidelines:

Any changes to the secure credential's value will automatically take effect across all monitors that use it. You do not need to also update the script.

Exception: If you update the script and jobs are already processing, the secure credential change will not take effect until the next time the job begins.

Security for secure credentials

To ensure the security of your secure credentials, New Relic scrubs the secure value out of all data that goes to results in synthetic monitoring data and alerts. New Relic employees cannot access secure credential values and must be added to the account to be able to view secure credentials.

Example

A secure credential is named PASSWORD and the value is Pass123!. New Relic replaces Pass123! with _SECURECREDENTIAL_

For example, a script includes:

$browser.get("https://example.com/" + $secure.PASSWORD)

The script results will show that New Relic Synthetics went to https://example.com/_SECURECREDENTIAL_, even though it actually went to https://example.com/Pass123!. This ensures the value of the secure credential will not appear in the results.

Redacted information

We currently redact the following from the results of your monitor:

• The exact values of your secure credentials
• Any percent-encoded values of your secure credentials