- Mais recentes
- Mais votos
- Mais comentários
Hello,
Thank you for reaching your question I understand that you are running into an issue with Cognito and open search. The first issue you are seeing is that after an arbitrary amount of time you are getting a CORS issue and the second issue is that you sometimes have to sign in twice. In order to best assist with this issue we would need to review the HAR file that you created that encompasses the error. I would recommend creating a ticket with AWS support where you can attach the relevant HAR file and an engineer can then assist with any additional troubleshooting for this specific issue.
Thank you.
I'm having the same issue. After I log in, I get this screen with this message:
Checking in the developer console, all requests raise this error (or similar, all related to CORS)
Access to <resource> at 'https://<cognito-subdomain>.auth.<region>.amazoncognito.com/login?response_type=code&client_id=<client_id>&redirect_uri=https://<os-subdomain>.<region>.es.amazonaws.com/_dashboards/app/home&state=<state>' (redirected from 'https://<os-subdomain>.<region>.es.amazonaws.com/_dashboards/ui/fonts/source_sans_3/SourceSans3-Light.otf.woff') from origin 'https://<os-subdomain>.<region>.es.amazonaws.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
What are we missing? Why is cognito not sending proper CORS policy?
Thank you,
I was able to make it work adding es:ESHttp*
action to the policy attached to the logged in user. Seems that the user needs to be able to perform all EShttp actions in the dashboard to use it properly.
Thank you,
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 3 meses
- AWS OFICIALAtualizada há 2 anos