My Oracle Support Banner

OHI Install Issue: "api" Failed to Preload on Startup in Web Application: "api". java.lang.IllegalStateException: No CORS Origins specified (Doc ID 2651703.1)

Last updated on APRIL 12, 2022

Applies to:

Oracle Health Insurance Enterprise Policy Administration - Version and later
Oracle Health Insurance Value-Based Payments - Version and later
Oracle Health Insurance Claims Adjudication - Version and later
Information in this document applies to any platform.


After upgrading, the following exception was thrown during deployment of the OHI Component:


<Servlet: "api" failed to preload on startup in Web application: "api".

java.lang.IllegalStateException: No CORS Origins specified; see the Security Guide for configuration details …


From the Security Guide, section 5.3 Cross Origin Resource  Sharing:

Oracle Insurance application provide support for CORS that requires configuration that is explained in the Installation Guide. At least allowed origins need to be specified, i.e. Oracle does not support the insecure '*' wildcard as a default as that would effectively mean that any traffic is allowed which violates the 'secure by default' installation principle.

CORS configuration is required. Without specifying allowed origins, Oracle Insurance

applications will not start.


When allowed origins are not specified, Oracle Insurance applications will fail to start with the following message: "No CORS Origins specified; see the Security Guide for configuration details


See also the Installation Guide for setting up the properties; See section "3.3 Configure OHI Policy Administration properties file" and scroll down to "Cross Origin Resource Sharing related properties."





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.