

Enabling CORS

Enable CORS configuration for API resources (API level)

If you are following the developer first approach, (deploy the API via CLI tool). You can add CrossOrigin Resource Sharing (CORS) configurations for each API (at API level) using the OpenAPI vendor extension x-wso2-cors in the API definition. The following code snippet depicts the usage of the x-wso2-cors extension. For more information, see the detailed sample OpenAPI definition with CORS level configuration.

x-wso2-basePath: /petstore/v1
x-wso2-production-endpoints:
  urls:
  - https://petstore.swagger.io/v2
x-wso2-cors:
  accessControlAllowOrigins:
    - test.com
    - example.com
  accessControlAllowHeaders:
    - Authorization
    - Content-Type
  accessControlAllowMethods:
    - GET
    - PUT
    - POST
  accessControlAllowCredentials: true

If you are following the Deploy API via API-M approach, you can add CORS configurations for each API using the MWARE ESB.

Enable CORS configurations globally

Follow the instructions below to enable CORS globally. Once this is enabled, it will apply this configurations through all endpoints and APIs deployed in Choreo Connect.

1. Open the Choreo Connect configuration file according to the deployment type you are using.

   Click here to see the configuration file location for your Choreo Connect deployment.

   Navigate to the correct folder path and open the config.toml or config-toml-configmap.yaml file based on your Choreo Connect deployment.

   Deployment	Mode	File name	Directory
   Docker Compose	Choreo Connect as a Standalone Gateway	config.toml	<CHOREO-CONNECT_HOME>/docker-compose/choreo-connect/conf/
   Docker Compose	Choreo Connect with MWARE ESB as a Control Plane	config.toml	<CHOREO-CONNECT_HOME>/docker-compose/choreo-connect-with-apim/conf/
   Kubernetes	Choreo Connect as a Standalone Gateway	config-toml-configmap.yaml	<CHOREO-CONNECT_HOME>/k8s-artifacts/choreo-connect/
   Kubernetes	Choreo Connect with MWARE ESB as a Control Plane	config-toml-configmap.yaml	<CHOREO-CONNECT_HOME>/k8s-artifacts/choreo-connect-with-apim/

2. Locate the following configuration set and make the enabled attribute to true with the required CORS attributes there.

   [router.cors]
       enabled = true
       allowOrigins = ["*"]
       allowMethods = ["GET","PUT","POST","DELETE","PATCH","OPTIONS"]
       allowHeaders = ["authorization","Access-Control-Allow-Origin","Content-Type","SOAPAction","apikey", "testKey", "Internal-Key"]
       exposeHeaders = []
       allowCredentials = false

Info

Global CORS configuration is enabled by default. Access control can be done by changing the parameters mentioned above.

Note

If CORS for a certain API is disabled from API Level Configurations, the default global Configurations will apply.

Top