Cloudpath connection settings

The dashboard’s Cloudpath Configuration page is where you tell CP Word List how to reach your Cloudpath server and how to display the passphrase. This page covers each field and the two identifiers you’ll need for the workflow setup.

Configuration fields

Field	What it is
Cloudpath FQDN	The hostname of your Cloudpath server, e.g. na1.cloudpath.net. This is also what activates your account — see Activate your account.
Cloudpath Username	The username of a Cloudpath API account the service uses to look up and update DPSKs.
Cloudpath Password	The password for that account. Enter it twice to confirm.
SSID Name	The Wi-Fi network name shown to the user on the enrollment page (“Connect to the MyWiFi network”).

Tip

Create a dedicated Cloudpath API account with only the permissions it needs, rather than reusing a personal admin login. The service authenticates to Cloudpath as this account on every passphrase change.

Your Cloudpath username and password are encrypted at rest and are never shown back to you — once saved, the fields read “Configured (encrypted)”. To change them, enter new values; leave them blank to keep the existing ones. For how credentials are protected, see Security controls.

Test Connection

After saving your FQDN and credentials, click Test Connection. The service authenticates to your Cloudpath server’s REST API using the stored credentials and reports success or the exact error.

Test Connection only works once your account is active. If your account is pending review, or the FQDN or credentials are missing, the test returns a message saying so. Common failures are covered in Troubleshooting.

Tenant ID and Shared Secret

The dashboard’s Cloudpath Workflow Setup section shows two identifiers you paste into Cloudpath:

• Tenant ID — identifies your account to the client-side lookup on the enrollment page.
• Shared Secret — authenticates the enrollment webhook. It’s included in the API Call URL you add to your Cloudpath notification step.

Both are generated for you. You can Regenerate Secret at any time — but doing so immediately invalidates the old one, so any Cloudpath workflow still using the old secret will start failing until you paste in the new API Call URL. See Add the enrollment workflow steps.

Caution

Treat the Shared Secret like a password. Anyone with it can trigger passphrase changes against your tenant. If it leaks, regenerate it and update your Cloudpath workflow with the new API Call URL.