Based on the information you provided, it seems that you have already taken several steps to address the CORS (Cross-Origin Resource Sharing) error when accessing your Aras Innovator instance through Ngrok tunneling. However, it appears that the issue persists.
Here are a few additional suggestions you can try to resolve the CORS error:
Double-check the modified line in the <customHeaders> section of the web.config file: Ensure that the value attribute is set correctly to "">https://xxx.yyy". Verify that there are no typos or extra spaces in the value.
Restart the Aras Innovator server: After making changes to the web.config file, it's essential to restart the Aras Innovator server for the modifications to take effect. Restart the server and check if the CORS error still occurs.
Verify the headers in the IIS Manager: Open the IIS Manager and navigate to your Aras Innovator instance. In the center pane, select "HTTP Response Headers" from the IIS section. Ensure that the headers you added are present and correctly configured with the expected values.
Test with a different tunneling solution: Since you mentioned that you are using Ngrok for tunneling, you might consider trying an alternative tunneling solution, such as localtunnel or ngrok alternatives like Serveo or PageKite. It's possible that using a different tunneling service could help bypass the CORS error. tunnel rush
Seek assistance from Aras Innovator community or support: If the issue persists despite your efforts, it would be beneficial to reach out to the Aras Innovator community or support team. They may have specific insights into configuring CORS for Aras Innovator instances or be able to provide additional troubleshooting guidance.
