Open the database → Credentials tab in my.cubepath.com.
Reveal the credentials
Credentials are hidden by default and only loaded when you explicitly click Reveal credentials. You get:
| Field | Use |
|---|---|
| Host and Port | For clients that take them separately |
| Username and Password | The admin account |
| Connection URI | A ready-to-paste string for most drivers and ORMs |
NoteEvery reveal is recorded in the activity log, with who did it and when. That's deliberate — credentials that grant full data access should leave a trail.
Two things can stop a reveal:
- The database is busy. Credentials are available once it settles into active or degraded. Wait for the current operation to finish.
- You don't have permission. Viewing credentials requires write access to managed databases. Ask an organization owner or admin.
Rotate the admin password
Rotate credentials generates a new admin password.
WarningThe current password stops working as soon as the rotation completes. Every application using it loses access until you update it. The database shows as updating while the rotation runs.
Rotate when the password may have been exposed — committed to a repository, pasted into a ticket, or held by someone who has left. The sequence that avoids an outage:
- 1Prepare the change firstHave the deployment ready to take a new password, so you're not editing config while your app is down.
- 2RotateConfirm the rotation and wait for the database to leave the updating state.
- 3Read the new passwordReveal credentials again to get it.
- 4Update and redeployPush the new value to your application and restart it.
Don't hand this out
The admin account is meant for administration, not for your application to connect with day to day. Create a dedicated user per application instead: one leaked application password then affects one application, and revoking it is a single delete rather than a rotation that breaks everything at once.