yellowfin silent installation ask not to reset password for admin user

Hi Ravindra,

Thanks for reaching out to Yellowfin support.

The default behavior of Yellowfin is to reset the password for the default user ('admin@yellowfin.com.au') during installation. However, you can modify the 'install.properties' file to set a custom password for the default user. Here's an example of how to do that:

1. Create a new file called password.properties with the following contents:

user.admin.password=myCustomPassword

Replace myCustomPassword with the password you want to set for the admin@yellowfin.com.au user.

2. Modify the install.properties file to include the following line:

-DresponseFilePath=<path_to_password.properties>

Replace <path_to_password.properties> with the full path to the password.properties file you created in step 1.

The modified command should look like this:

java -jar yellowfin-8.0.11-20220223-full.jar -silent install.properties -DresponseFilePath=<path_to_password.properties>

By setting a custom password for the default user in the password.properties file and passing it to the installation script using the -DresponseFilePath parameter, you can prevent the default password from being set during installation.

Let me know how it goes.

Regards,

Sri Vamsi

does the password need to be in encoded / plain text

Hi

does the password need to be in encoded / plain text

thanks

Ravindra

Hi Ravindra,

Thanks for your reply.

The password should be plain text. You don't need to encode or encrypt it in any way. When you set the password in the 'password.properties' file, Yellowfin will use it as plain text and hash it internally before storing it in the database.

Regards,

Sri Vamsi

I tried the steps given by you and they do not seem to be working.

Created password.properties file:

user.admin.password=xxxxxxx

Updated install.properties file to add below line:

DresponseFilePath=/tmp/password.properties

Ran the command:

java -jar yellowfin-8.0.11-20220223-full.jar -silent install.properties -DresponseFilePath=/tmp/password.properties

Below is the log:

[root@ct-cp-yellowfin-prod-407812 tmp]# java -jar yellowfin-8.0.11-20220223-full.jar -silent install.properties -DresponseFilePath=/tmp/password.properties
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
Feb 17, 2023 5:15:55 PM liquibase.lockservice
INFO: Successfully acquired change log lock
Feb 17, 2023 5:15:56 PM liquibase.changelog
INFO: Reading from yellowfin.DATABASECHANGELOG
Feb 17, 2023 5:15:56 PM liquibase.lockservice
INFO: Successfully released change log lock
Feb 17, 2023 5:15:56 PM liquibase.lockservice
INFO: Successfully acquired change log lock
Skipping auto-registration
Feb 17, 2023 5:15:56 PM liquibase.hub
WARNING: Skipping auto-registration
Feb 17, 2023 5:15:56 PM liquibase.changelog
INFO: Continuing past: com/hof/patch/db-schema-changelog-8.0.xml::YFN-21641 Increase FormatCode to fit encrypted passwords for SQL Server::pd despite precondition failure due to onFail='CONTINUE':
com/hof/patch/db-schema-changelog-master.xml : DBMS Precondition failed: expected mssql, got mysql

Feb 17, 2023 5:15:56 PM liquibase.lockservice
INFO: Successfully released change log lock
Feb 17, 2023 5:16:15 PM liquibase.lockservice
INFO: Successfully acquired change log lock
Feb 17, 2023 5:16:15 PM liquibase.changelog
INFO: Reading from yellowfin.DATABASECHANGELOG
Feb 17, 2023 5:16:15 PM liquibase.lockservice
INFO: Successfully released change log lock
Feb 17, 2023 5:16:15 PM liquibase.lockservice
INFO: Successfully acquired change log lock
Skipping auto-registration
Feb 17, 2023 5:16:15 PM liquibase.hub
WARNING: Skipping auto-registration
Feb 17, 2023 5:16:15 PM liquibase.lockservice
INFO: Successfully released change log lock
Feb 17, 2023 5:16:17 PM liquibase.lockservice
INFO: Successfully acquired change log lock
Feb 17, 2023 5:16:17 PM liquibase.changelog
INFO: Reading from yellowfin.DATABASECHANGELOG
Feb 17, 2023 5:16:17 PM liquibase.lockservice
INFO: Successfully released change log lock
Feb 17, 2023 5:16:17 PM liquibase.lockservice
INFO: Successfully acquired change log lock
Skipping auto-registration
Feb 17, 2023 5:16:17 PM liquibase.hub
WARNING: Skipping auto-registration
Feb 17, 2023 5:16:17 PM liquibase.changelog
INFO: null
Feb 17, 2023 5:16:17 PM liquibase.changelog
INFO: ChangeSet com/hof/util/liquibase/db-runalways.xml::YFN-9269 Insert schema version and schema release in Configuration::cesar ran successfully in 35ms
Feb 17, 2023 5:16:17 PM liquibase.changelog
INFO: Continuing past: com/hof/util/liquibase/db-runalways.xml::YFN-9269 Update schema version and schema release in Configuration::cesar despite precondition failure due to onFail='CONTINUE':
com/hof/installer/process/job/liquibase/db-customclasses-installer-master.xml : Expected changelog property 'installer.type' to have a value of 'patcher'. Got 'installer'

Feb 17, 2023 5:16:17 PM liquibase.lockservice
INFO: Successfully released change log lock
[root@ct-cp-yellowfin-prod-407812 tmp]#

Hi Ravindra,

Can you please share the Yellowfin installation log errors. Unfortunately, I'm unable to get Yellowfin errors from below logs.

Based on the information in the console log you provided, the Liquibase update process is failing due to a DBMS precondition failure. The log indicates that the expected DBMS (Database Management System) is "mssql", but the actual DBMS is "mysql".

Regards,

Sri Vamsi

Hi Ravindra,

I just want to touch base to see if you had chance to read through my response. If you can let me know that would be great.

regards,

Sri Vamsi

Hi Ravindra,

I'm going to go ahead and mark this ticket as Completed due to inactivity at this time. Feel welcome to reach out in the future.

Regards,

Sri Vamsi