Each fresh installation of the console uses the same default passwords; after installing the console, you should modify the passwords used by the console to create a more secure environment.A fresh installation of the Ark console includes a PostgreSQL installation that is used to manage the console; the management database is named postgres. By default, the database superuser has the following connection credentials:name: postgrespassword: c3accd4604514ec58927a462379020fa1f643a0bYou should change the database superuser's password on the PostgreSQL server to a unique password (known only to trusted users). After changing the superuser password on the PostgreSQL database, you will need to copy that password to the JDBC connection pool. If you have enabled console backups, you must also modify the ppcd.properties file and the .pgpass file.You can use the SQL ALTER ROLE command and the psql client to change the password on the Postgres server. To start the psql client, the bin directory must be in your search path. At a terminal window, connect to the psql client with the command:When prompted, supply the password of the postgres database user. After connecting to the database, you can use the ALTER ROLE command to modify the password associated with the postgres user:ALTER ROLE postgres password 'new_password';new_password is the new password of the postgres role.After modifying the password associated with the database superuser, use the \q meta-command to exit the psql client.After changing the password of the database superuser, you must also change the password in the JDBC connection pool. At the command line, assume the identity of the ppcd user:new_password is the password of the postgres role.After modifying the password for the JDBC connection pool, you can ping the connection pool to test the jdbc connector. Use the command:remote failure: Ping Connection Pool failed for pcsconfig-pool.
Connection could not be allocated because: FATAL: password authentication failed for user "postgres" Please check the server.log for more details.If you have enabled console backups, you must also modify the ppcd.properties files, adding the new password:console.db.password=new_passwordThen, modify the .pgpass file, replacing the old password associated with the postgres role with the new password. By default, the .pgpass file is located in the home directory of the ppcd user (~ppcd). Use your choice of editor to modify the .pgpass file, updating the password.name: adminpassword: ChangeIt2015!To modify the password associated with the GlassFish user, use ssh to connect to the console image, authenticating yourself with the account id and key pair used when the instance was created (See Section 3.3). Then, assume the identity of the ppcd user:Then, use the asadmin utility to change the password (see Figure 6.1). The utility will prompt you through the process of resetting your password:Provide the password associated with the administrative user and press Return; by default, the password is ChangeIt2015!.Confirm the new password, and press Return. The asadmin utility will confirm:If you are use the asadmin utility often (for example, starting and stopping the console server), you can use the asadmin login command to save the credentials for the current connected user. Use ssh to connect to the console image, and invoke the command:Provide a user name and press Return.Provide the password associated with the user, and press Return. The console will respond:Login information relevant to admin user name [admin]
for host [localhost] and admin port  stored at
Make sure that this file remains protected.
Information stored in this file will be used by
asadmin commands to manage the associated domain.
Command login executed successfully.