Duaer

Integrations

Set up WordPress credentials in Duaer

Store WordPress 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 WordPress with an application password

For self-hosted WordPress, use the Duaer Wordpress API credential with an application password, not your sign-in password:

  1. In the WordPress admin, open Users > Profile, name a new entry under Application Passwords, click Add New Application Password, and copy the password.
  2. Put that user name in Username, the application password in Password, and the site home page, such as https://blog.example.com, in Wordpress URL.

Application passwords need the site on HTTPS. Turn on Ignore SSL Issues (Insecure) only for a self-signed certificate.

For sites hosted on WordPress.com, use WordPress OAuth2 API: create an app at WordPress.com Developer, set Redirect URLs to the Duaer OAuth Redirect URL, and put the site domain in WordPress.com Site. The credential dialog says OAuth2 works only with sites hosted on WordPress.com.

Wordpress API

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

  • Username
  • Password (secret)
  • Wordpress URL
  • Ignore SSL Issues (Insecure): Whether to connect even if SSL certificate validation is not possible. Default: off.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Wordpress.

WordPress OAuth2 API

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

  • Client ID (required)
  • Client Secret (required, secret)
  • WordPress.com Site (required): Your WordPress.com site identifier — either a .wordpress.com subdomain (e.g. myblog.wordpress.com) or a custom domain (e.g. myblog.com). Used in API requests that still route through public-api.wordpress.com.
  • Custom Scopes: Whether to define custom OAuth2 scopes instead of the defaults. Default: off.
  • Enabled Scopes: Space-separated list of OAuth2 scopes to request. Default: global. Shown when Custom Scopes is on.

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Note from the dialog: OAuth2 authentication works with WordPress.com-hosted sites only. For self-hosted WordPress, use the WordPress API (Basic Auth) credential instead.

Duaer nodes that use it: Wordpress.

Save the connection in Duaer

Open Credentials and create WordPress. 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 WordPress secret values appear in Duaer node parameters?

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

What usually stops a WordPress 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 WordPress expects, then confirm you can create credentials in that project.

In this section