InfoSphere Information Governance Catalog import failed with message "An error occurred on . "

-

Problem(Abstract)

InfoSphere Information Governance Catalog (IGC) Import failed with message "An error occurred on <timestamp>. Further details may be found in the server logs or browser console", but no error is displayed in the igc.log file

Symptom

InfoSphere Information Governance Catalog Import displays at the end of the import the message "An error occurred on <timestamp>. Further details may be found in the server logs or browser console" as "Import Summary", but the assets (Categories, Terms , ...) were imported.


Cause

To prevent cross-frame scripting attacks, the value of the com.ibm.iis.gov.xFrameOptions could be set to 'DENY'. This value cause this error message at the end of the import, in spite of import ended successfully.

Unfortunately, this value ('DENY') was previously recommended by the documentation for the configuration of InfoSphere Information Governance Catalog.


Diagnosing the problem

In spite of the "Import Summary" message, the igc.log file demonstrates that the Import is successful.

Extract of the igc log file in line with the error message:


2015-04-03 13:10:16,829 INFO  xml.GlossaryXMLImport - Start importing glossary XML in one chunk
2015-04-03 13:10:16,895 INFO  aiimport.ImportUtils - Generating workflow metadata...
2015-04-03 13:10:16,897 INFO  aiimport.ImportUtils - Workflow metadata creation done.
2015-04-03 13:10:16,900 INFO  aiimport.ImportUtils - Synching assigned assets...
2015-04-03 13:10:16,900 INFO  xml.GlossaryXMLImport - Glossary XML import completed successfully.


Resolving the problem

Change the value of the bg.xFrameOptions to SAMEORIGIN on the Service tier.

cd IS_install_path/ASBServer/bin                                        
./iisAdmin.sh -set -key com.ibm.iis.gov.xFrameOptions -value SAMEORIGIN
(SAMEORIGIN to replace DENY)


Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more