This issue only becomes visible when sap_swpm_master_password is different to sap_swpm_db_schema_abap_password AND sap_swpm_product_catalog_id doesn't contain the word ABAP which is e.g. during AAS installation.
The behaviour is that will attempt to install the AAS instance using sap_swpm_master_password as the schema password. This works if both passwords happen to be the same, but fails if they are different.
The culprit is the code in:
password_facts.yml
The variable sap_swpm_db_schema_password which is used in the configfile template, is set here based on whether it's java or abap system. Unfortunately when installing AAS (possibly others?) the catalog_id for AAS doesn't contain the word ABAP (NW_DI:S4HANAXXX.CORE.HDB.PD). The code then doesn't set sap_swpm_db_schema_password which means SWPM will use the master password instead.
Possible solution can be to add "or" and match the AAS catalog ID, but I am suspecting that this may be the same or similar to Java AAS which I can't test. So I didn' t feel it would be safe to change it.
As a workaround there is a pull request #760 for the sample var file which explicitly adds and sets sap_swpm_db_schema_password.
This issue only becomes visible when
sap_swpm_master_passwordis different tosap_swpm_db_schema_abap_passwordANDsap_swpm_product_catalog_iddoesn't contain the word ABAP which is e.g. during AAS installation.The behaviour is that will attempt to install the AAS instance using
sap_swpm_master_passwordas the schema password. This works if both passwords happen to be the same, but fails if they are different.The culprit is the code in:
password_facts.yml
The variable
sap_swpm_db_schema_passwordwhich is used in the configfile template, is set here based on whether it's java or abap system. Unfortunately when installing AAS (possibly others?) the catalog_id for AAS doesn't contain the word ABAP (NW_DI:S4HANAXXX.CORE.HDB.PD). The code then doesn't setsap_swpm_db_schema_passwordwhich means SWPM will use the master password instead.Possible solution can be to add "or" and match the AAS catalog ID, but I am suspecting that this may be the same or similar to Java AAS which I can't test. So I didn' t feel it would be safe to change it.
As a workaround there is a pull request #760 for the sample var file which explicitly adds and sets
sap_swpm_db_schema_password.