By creating a cross-origin resource sharing (CORS) policy and subsequently mapping it to an application REST endpoint (path or URL), you control whether and how other systems or websites (origins) can access that resource.
- In the header of Dev Studio, click .
- On the Cross Origin Resource Sharing form, in the Short description field, enter a description of the CORS policy.
- In the Policy name field, enter a name for the CORS policy. You might name the policy for an endpoint, or for the API or REST service that you want to protect.
- Click Create and open.
- On the Cross Origin Resource Sharing form, on the Policy Definition tab, select the Allow credentials check box to indicate that requests to the endpoint can include credentials.
- In the Allowed origins field, enter a comma-separated list of
domains (origins) that are allowed to make a request against the API or REST
service.At run time, the system evaluates all origins that you specify for this setting until it finds a match for the origin header of the request. Wildcard characters are also supported.
- In the Maximum age field, enter a number to specify how long, in
seconds, the results of a preflight request can be cached.This is the time period between two consecutive preflight requests, within which you do not want the web browser to send a new preflight request. A longer period reduces the frequency of browser preflight OPTIONS method call requests.
- In the Allowed methods section, select one or more check boxes to specify which request methods are allowed: GET, POST, PUT, PATCH, or DELETE.
- In the Allowed headers section, enter a comma-separated list of
the request header values that the origin domain is allowed to use for a CORS
request.The authorization and content-type headers are required for Pega Platform applications.
The default value is: authorization, content-type
- In the Exposed headers section, enter a comma-separated list of response headers that clients of this API or service can access.
- Click Save.