IG 4.2 - workflow-api: Unable to decrypt data because no keys have been supplied

Hi,
after upgrading from IG 3.7.2 to 4.2 I get an error on starting tomcat:

[SCHWERWIEGEND] 2024-01-31 13:19:17.771 [com.netiq.iac.workflow.jee.IacWorkflowServerInitListener] Error initializing logging
java.lang.IllegalStateException: Unable to decrypt data because no keys have been supplied.
        at com.netiq.ism.obfuscate.CryptoUtils.decrypt(CryptoUtils.java:437)
        at com.netiq.ism.obfuscate.CryptoUtils.decipher(CryptoUtils.java:403)
        at com.netiq.ism.config.impl.ConfigurationImpl.decode(ConfigurationImpl.java:835)
        at com.netiq.ism.config.impl.ConfigurationImpl.getString(ConfigurationImpl.java:417)
        at com.netiq.iac.common.logging.ArcLoggingConfigurator.getConfigString(ArcLoggingConfigurator.java:283)

Currently I think this happens because my system is missing configurations in ism-configuration.properties:

# fgrep wfe ism-configuration.properties
com.microfocus.wfe.consumer.url = https://abc:8443/api/wfi
com.microfocus.wfe.consumer.password._attr_obscurity = ENCRYPT

My working reference system lists:

# fgrep wfe ism-configuration.properties
com.microfocus.wfe.consumer.url = https://def:8443/api/wfi
com.microfocus.wfe.consumer.userId = workflow
com.microfocus.wfe.consumer.password._attr_obscurity = ENCRYPT
com.microfocus.wfe.consumer.password = [AES/GCM/NoPadding]6xXXX:r/Harr18/t2XXXc9fXXX==

Any ideas where this configuration is coming from? Can neither find it in configupdate.sh nore in configutil.sh.

regards
Daniel

Parents Reply Children
  • 0   in reply to 

    Hello,
       At this point, I would suggest opening a Service Request with Support. We will need to get some information from your environment that should not be shared here.

    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    OpenText Cybersecurity

  • 0 in reply to 

    As Steven said, "workflow-api.war" is no longer in use. So I "solved" it by removing the war-file Slight smile

    I had an error in IG which I _tought_ is related to this exception, but it turned out the error was something completely different. So having "workflow-api.war" still in webapps should not effect your IG, if I understood it correctly.

    regards
    Daniel