We have a self-hosted octopus server and we are utilizing the octopus API.
Under Configuration → Web Portal ->CORS whitelisting, we added comma-separated values and ran into CORS errors from the consuming application. However a wildcard works
Working whitelist values : *
Whitelist values that do not work :
So unfortunately you wouldn’t be able to use domain-specific wildcards for this within Octopus Deploy as the valid values are determined by the CORS specification itself, and you would instead either need to use a global wildcard or the specific domain(s)/subdomain(s), protocol(s), and port(s).
Sorry I don’t have better news for you on this, but let me know if you have any additional questions or if I can be of any more help and I would be glad to assist further.