Integrations
Set up F5 Big-IP credentials in Duaer
Store F5 Big-IP 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.
Connect F5 BIG-IP with an iControl REST account
The Duaer F5 Big-IP API credential calls iControl REST with a BIG-IP user name and password:
- Create a dedicated account under System > Users in BIG-IP with only the role it needs; terminal access can stay off.
- Put the account in Username and Password. The BIG-IP management address goes in the HTTP Request node URL, such as https://bigip.example.com/mgmt/tm/ltm/pool.
Duaer has no dedicated node for this service. In the HTTP Request node, set Authentication to Predefined Credential Type and pick the F5 Big-IP API credential. Refer to custom operations.
F5 Big-IP API fields in Duaer
In Duaer, choose F5 Big-IP API when you create a credential, then fill in these fields:
- Username (required)
- Password (required, secret)
Save the connection in Duaer
Open Credentials and create F5 Big-IP. 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.
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 F5 Big-IP secret values appear in Duaer node parameters?
No. In Duaer, F5 Big-IP secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a F5 Big-IP 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 F5 Big-IP expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.