This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Allow more control for CORS configuration: Allow pattern matching with wildcards when configuring CORS tag in server.xml
System: WebSphere Liberty Profile Actor: Integration from different domains when using front-end Libs such as Angular and micro service back-ends
WebSphere Liberty is commonly used in cloud worlds serving micro services and integration REST APIs. In the cloud world it is common, that these services have their own host name (i.e. backend1.mycomany.com, backend2.mycomany.com, backend3.mycomany.com) while the GUIs might run under gui.mycomany.com and another one under gui2.mycompany.com.
Liberty provides a tag called cors that allows you to transparently for the application configure CORS support. This works fine, but is restricted. You can either hardcode the value, or allow everything by setting "*".
The most common identifier used is the origin. To have more control, it would be beneficial to allow not only "*" by itself, but with some pattern matching. For the above example, allowedOrigins="*.mycompany.com" would allow only the appropriate GUI to access the services.
Today, as soon as the allowedOrigins contains a * it allows every origin.
Do not place IBM confidential, company confidential, or personal information into any field.