How to configure CORS Headers in Service Registry ?

Solution Verified - Updated -

Issue

  • How to configure CORS Headers in Service Registry to avoid the following exception:

    apicurioregistry-kafkasql.dev-apicurio.router-default.apps.test.cloud/:1 Access to XMLHttpRequest at 
'https://login.test.com/auth/realms/internal/protocol/openid-connect/token' from origin 'http://apicurioregistry-kafkasql.dev-apicurio.router-        
 default.apps.test.cloud' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
  keycloak.js:795          POST https://login.test.com/auth/realms/internal/protocol/open

Environment

  • Red Hat Service Registry: 2.x
  • Red Hat OpenShift Container (Openshift) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content