Creating secure credentials (a combination of username and password) is of paramount importance in protecting production systems. It is imperative that you choose a secure password for the database user and it is recommended that you use a unique username. The password used will also have to conform to the MySQL password validation policy described above.
uniquename and a password of Z9hfB#qta8YfUB{va6K (a long, randomly generated password or pass phrase is recommended), type the following at the MySQL command prompt followed by pressing the Return key:
CREATE USER 'uniquename'@'localhost' IDENTIFIED WITH mysql_native_password BY 'Z9hfB#qta8YfUB{va6K';The
WITH mysql_native_passwordportion of the command may not be supported on earlier versions of MySQL. If an error occurs, removeWITH mysql_native_passwordand reissue the command.On non-production (i.e., "testing" or "staging") systems, the default username of
jamfsoftwareand the default password ofjamfsw03may be used to avoid having to provide custom values when the Jamf Pro web application first launches, but these should not be used for production systems.
localhost with the IP address of the remote server that will be trying to communicate with MySQL (i.e., the Jamf Pro web application server), as in this example:CREATE USER 'uniquename'@192.168.22.22 IDENTIFIED WITH mysql_native_password BY 'Z9hfB#qta8YfUB{va6K';It is also necessary to configure the bind-address in the MySQL configuration file so that MySQL is "listening" for communication coming from this IP address.
In a clustered environment, there are many other settings that will need to be addressed.