update cors to allow schema-registry-ui to connect

[ceastman-ibm]

https://www.bountysource.com/issues/74857052-connectivity-error-with-schema-registry-5-2-1

[ghost]

It looks like @ceastman-ibm hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.

Once you've signed reply with [clabot:check] to prove it.

Appreciation of efforts,

clabot

[ceastman-ibm]

clabot:check

[ceastman-ibm]

[clabot:check]

[ghost]

@confluentinc It looks like @ceastman-ibm just signed our Contributor License Agreement. 👍

Always at your service,

clabot

[ceastman-ibm]

@rayokota Does this look good to you?

[OneCricketeer]

I feel like the current defaults are fine, assuming requests are from the same domain. These options are left up to be configured by the end user, and enabling all domains to access all methods is probably too broad.

These lines could be listed, but commented out to mention why they'd be used (without specifically saying a 3rd party tool).

Connect REST API also has these options, by the way, but these aren't listed there for having the connect UI work

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}