You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
Teleport would proxy requests from one app to another without CORS error.
Current behavior:
Currently we are getting the following CORS error:
Access to fetch at 'https://test-auth.teleport.test.us/v2/test/auth' from origin 'https://test.teleport.test.us' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Bug details:
Teleport version: 17.0.5
Recreation steps
Hitting the test app hits an AWS Amplify endpoint and works without issue. This then produces a login page. The actual authentication hits the test-auth app which redirects to a backend service that does SAML auth. It never gets that far. The browser kills it with the error above. Preflight does work though. I have no issues turning off CORS for these apps if possible and the easiest way forward.
The actual authentication hits the test-auth app which redirects to a backend service that does SAML auth. It never gets that far. The browser kills it with the error above.
It looks like you've correctly configured allowed_origins for the test-auth app. Can you share the response to the preflight request? Is the Access-Control-Allow-Origin header present?
Expected behavior:
Teleport would proxy requests from one app to another without CORS error.
Current behavior:
Currently we are getting the following CORS error:
Access to fetch at 'https://test-auth.teleport.test.us/v2/test/auth' from origin 'https://test.teleport.test.us' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Bug details:
Teleport version: 17.0.5
Recreation steps
Hitting the test app hits an AWS Amplify endpoint and works without issue. This then produces a login page. The actual authentication hits the test-auth app which redirects to a backend service that does SAML auth. It never gets that far. The browser kills it with the error above. Preflight does work though. I have no issues turning off CORS for these apps if possible and the easiest way forward.
Config
The text was updated successfully, but these errors were encountered: