Duaer

Integrations

Set up SecurityScorecard credentials in Duaer

Store SecurityScorecard connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Get a SecurityScorecard API key

The Duaer SecurityScorecard API credential needs one key:

  1. In SecurityScorecard, open My Settings > API and generate an API token.
  2. Put it in API Key and save.

SecurityScorecard API fields in Duaer

In Duaer, choose SecurityScorecard API when you create a credential, then fill in these fields:

  • API Key (required, secret)

Duaer nodes that use it: SecurityScorecard.

Save the connection in Duaer

Open Credentials and create SecurityScorecard. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do SecurityScorecard secret values appear in Duaer node parameters?

No. In Duaer, SecurityScorecard secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a SecurityScorecard credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields SecurityScorecard expects, then confirm you can create credentials in that project.

In this section