Skip to content

Knowledgebase

Creating a database and scoped user in Webuzo

control-panels, development

Create a separate database and scoped database user for each application where practical. The website needs its own credentials and permissions; it should not connect using the database server root account.

Check access and requirements

Confirm the application database engine and supported version. This guide describes the MySQL or MariaDB workflow, not PostgreSQL or MongoDB. Check account allowances and decide the database name, username and required privileges before configuring the application.

01 Create a database and scoped user in Webuzo

  1. Open Database > Database Wizard in the end-user panel. Create the application database and note the full resulting name, including any account prefix.
  2. Create a dedicated database user with a unique strong password. Store it in your password manager or protected deployment secret store, not in a public file.
  3. Add the user to the exact database. Select the privileges the application requires; an installer may require schema-changing permissions that a steady-state runtime does not need.
  4. Enter the full database name, user, password and documented host in the application private configuration. Do not assume that the visible short name is the complete SQL identifier.
  5. Run the application connection or installation test. Keep configuration files outside the document root where the application supports that arrangement.
  6. If remote access is necessary, separately authorize the specific client host and secure the network path. Do not enable unrestricted remote database access merely to make a local application connect.

Does creating a database user grant access automatically?

No. Complete the user-to-database assignment and privilege step. A valid credential without permission on the application database can still produce an access-denied error.

Confirm the expected result

Confirm the application can read and perform an intended write in its own database. Verify that its user is not assigned to unrelated databases. Include the database in backups and test that its credentials are restored or rotated appropriately during recovery.

Resolve setup problems

For access denied, compare the full username, host and password with the assigned database privileges. For unknown database, check the full prefixed name. Avoid resetting the global database root password or granting every server privilege to solve a single application credential error.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support