Safenames

Safenames does not support read-only API keys

It's important to note that Safenames does not support read-only API keys, so we need to connect using a Safenames user account. We highly recommend that you connect using a dedicated user account created for Certificates only with security level 5 (View). 2FA must be disabled in this user account, so please use strong and long passwords that are unique to this integration.

Information required to configure the integration

To configure the integration you need:

• the username and password for the Safenames user account. To create a new user account:
  • Please login into the Safenames account using an existing user account with Level 1 (Administrator) permissions.
  • Go to Users.
  • Click 'Add New User'.
    • Add a meaningful username (like certificates_integration).
    • Use a shared email address.
    • Pick Level 5 (View) as the security level.
    • Leave SAO approver unticked.
    • Use a strong and long password that is unique to this integration only.
  • Keep a note of the username and password for the account.
• A unique reference to identify the Safenames account such as the account user name. This is important as there may be more than one Safenames account added to your organization.

Configuring the integration in Certificates

Once you have all of the information required, you can configure the integration in Certificates. Go to Integrations. Then:

• Click 'Add New Integration' and select Safenames.
• Then enter:
  • 'Name' - a mandatory field. The name you would like to use for this integration. Use something that will make sense to you and your team.
  • 'Safenames Customer ID' - a mandatory field. This should be something unique to your organizations Safenames account.
  • 'Tags' - this is optional. When this feature is used, then Certificates will tag any resources that we discover when running the integration.
  • 'Username' - a mandatory field. This is the username created in the previous step.
  • 'Password' - a mandatory field. This is the password created in the previous step.
  • Click "Save Integration".
    • Once saved, click "Test" in the integration's actions in the table. If it succeeds, then ensure the integration is enabled and enable it otherwise using the row actions. Your new integration is now active and will run shortly.
    • If we have been unable to connect, then the error 'Invalid credentials' will be shown at the top right-hand side of the page.

Adding discovered domains to your Certificates inventory

Rather than immediately adding domains from integrations to your Certificates inventory, we give you the opportunity to review them first. This means you can check that they should be added to your Certificates inventory, and if so whether the domain should be monitored or not.

• The domains that have been discovered in your CSC account can be reviewed in Discovered Hosts. They will be labeled in 'Match Reason' as 'Integration - Name', with the name being what you called the integration when you added it.
• If you would like to add a domain to the Certificates inventory, then select it, click 'Update n hosts', then mark them as 'Own'. This tells Certificates that you own those domains. They will be added to your inventory, and monitoring will begin immediately.
• If you would prefer to delete a discovered domain, then pick 'Delete' instead of 'Own'.

Common issues

If the integration fails then check that the:

• Username has been correctly copied.
• The password has been correctly copied.
• that the Safenames user account used has 2FA disabled.