Omni Administrator cannot use an OSGi configuration file to manage portal instance level CORS settings

• Type: Impedibug
• Status: Closed
• Priority: Minor
• Resolution: Discarded
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Application Security
• Labels: None
• Sprint: Iteration 36, Iteration 37, Iteration 38, Iteration 39, Iteration 40, Iteration 41, Iteration 42, Iteration 43, Iteration 44, Iteration 45

Steps to reproduce:

1. Navigate to Control Panel>Configuration>Virtual Instances
2. Create a new virtual instance named as "www.able.com".
3. Login as instance admin [e-mail].
4. Navigate to Instance Settings > Security Tools
5. Click on Add button
6. Type in “Instance 1” into the Name input field
7. Add a new url pattern of /url/pattern/one/*
8. Use default values for all other fields
9. Click the Save button
10. Assert that a Success alert message appears
11. Assert that the “Instance 1” configuration entry displays in the table
12. Export the “Instance 1” configuration entry and save the config file
13. Delete the “Instance 1” configuration entry
14. Shut down portal
15. Put the previous config file(com.liferay.portal.remote.cors.configuration.PortalCORSConfiguration-3d8e1954-38bc-4d54-973a-9fcb96fd4560.config) into \osgi\configs folder
16. Start up portal
17. Login as instance admin [e-mail].
18. Navigate to Instance Settings > Security Tools

Expected Result: “Instance 1” configuration entry should display in www.able.com instance setting.

Acutal Result: “Instance 1” configuration entry displays in portal system setting.