• State Suggested Answer
  • Replies replies
    3
  • Answers answer
    1
  • Subscribers subscribers
    16
  • Views views
    165
  • Users 0 members are here

IGA 4.3.1 Issues -- Tomcat not starting properly giving a blank screen .

Cap Vcc

When trying to upgrade or do a fresh installation to IGA 4.3.1 I am facing the below issue .Can someone help me on this case .

[SEVERE] 2024-10-30 14:52:45.854 [com.microfocus.logging.config.LoggingConfigurator] Error initializing logging java.lang.IllegalStateException: com.netiq.ism.obfuscate.NoSecretKeyException: Unable to decrypt data with any of the 2key(s) at com.netiq.ism.obfuscate.CryptoUtils.decipher(CryptoUtils.java:512) at com.netiq.ism.config.impl.ConfigurationImpl.decode(ConfigurationImpl.java:896) at com.netiq.ism.config.impl.ConfigurationImpl.getString(ConfigurationImpl.java:430) at com.microfocus.logging.config.LoggingConfigurator.extractLoggingConfiguration(LoggingConfigurator.java:574) at com.microfocus.logging.config.LoggingConfigurator.initLogging(LoggingConfigurator.java:357) at com.netiq.iac.common.logging.ArcLoggingConfigurator.initLogging(ArcLoggingConfigurator.java:115) at com.netiq.iac.common.j2ee.IacBaseInitListener.contextInitialized(IacBaseInitListener.java:66) at com.netiq.iac.server.j2ee.ArcServerInitListener.contextInitialized(ArcServerInitListener.java:128) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4007) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4448) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:599) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:571) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:603) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1014) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1866) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:816) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:468) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1584) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312)

I am getting this error in IGA 4.3.1 and all the components have been upgraded successfully without any error and only receiving this error when restarting the tomcat service .

Can someone guide me what to do .

  • 0  

    Hello,

    1.a) Is OSP installed locally?
    1.b) If installed locally, did you upgrade it?
    1.c) If installed lcoally, did you elect to create a new Encryption key or use an existing one?


    2.a) What version of Identity Governance did you upgrade from?
    2.b) During the IG install, did you elect to create a new Encryption key or use an existing one?


    In general, this kind of error occurs because:
    a) One created a new encryption during the OSP install and then created another new one during the IG install
    b) When upgrading from 4.2 to 4.3.1, one creates a new encryption key instead of utilizing one created during the 4.2 install
    c) Access rights to the file

    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    OpenText Cybersecurity

  • 0 in reply to   

    1) OSP is installed locally 

    2)I have created a new encryption key when it opted for in osp .

    3)I used the same encryption keys when it came when installing identity Governanace but still getting the same issue .

    4)I am doing a fresh install of 4.2 on the server and after that I removed everything and done a fresh install of 4.3.1 .

    Do I need to use the same encryption keys when I installed in 4.2 .

    I am not using upgrade helped scripts and directly used the install helper scripts .

    Can you guide me what went wrong .

  • Suggested Answer

    0   in reply to 

    Hello,


    "4) I am doing a fresh install of 4.2 on the server and after that I removed everything and done a fresh install of 4.3.1 ."

    That is not the correct way to upgrade from 4.2.0 to 4.3.1. Starting with 3.6.1, we support in-place upgrading. There is no reason to uninstall the product.

    "2)I have created a new encryption key when it opted for in osp "
    "Do I need to use the same encryption keys when I installed in 4.2 ."

    When upgrading (or installing a new node into the cluster), you will utilize the existing encryption key that was previously created.

    C)Installation and Upgrade
    1) IG 4.2 Installation with OSP from IG media:
    -Create a new Encryption key during the OSP install on node1.
    -During the IG install on node1, utilize existing Encryption key created above

    If creating a cluster, then on the next node, one will copy the encryption key and the ism-sensitive.properties from node1 to nodeX
    -During the OSP install on nodeX, utilize existing Encryption key created above
    -During the IG install on nodeX, utilize existing Encryption key created above


    2) Upgrading from IG 4.2 to 4.3.1 with OSP from IG media:
    -During the OSP install, utilize existing Encryption key created during the 4.2 install
    -During the IG install, utilize existing Encryption key created during the 4.2 install


    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    OpenText Cybersecurity

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.