Aws-cli: [V2] Issue Validating Terminal Code in website

Created on 12 Nov 2019  路  10Comments  路  Source: aws/aws-cli

Hi All!

I tried to following this (https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html) and when i arrived to web validate code appear in terminal the website show the next error.

Unexpected Error TypeError: Failed to fetch

Any ideas?

Version:
aws-cli/2.0.0dev0 Python/3.7.4 Darwin/18.7.0 botocore/2.0.0dev0

v2

Most helpful comment

While that is the issue:

VM14:1 Refused to connect to 'https://oidc.ap-southeast-2.amazonaws.com/device_verification?user_code=******' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.

VM14:1 Refused to connect to 'https://oidc.ap-southeast-2.amazonaws.com/device_verification?user_code=******' because it violates the document's Content Security Policy.

disabling security features in a browser is not a solution.

All 10 comments

Getting the same error on Mac/Linux/Windows with Chrome/Safari and Firefox browsers.

You need to disable browser content security policy then it should work

You need to disable browser content security policy then it should work

Where is this in Chrome/Firefox/Safari?

While that is the issue:

VM14:1 Refused to connect to 'https://oidc.ap-southeast-2.amazonaws.com/device_verification?user_code=******' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.

VM14:1 Refused to connect to 'https://oidc.ap-southeast-2.amazonaws.com/device_verification?user_code=******' because it violates the document's Content Security Policy.

disabling security features in a browser is not a solution.

Also, can someone attach the V2 label to this issue so it gets some visibility?

@holmesjr You're correct. We do not recommend disabling CSP to work around this issue.

This was a bug in the console page that I've been told has since been fixed. You may need to clear you browser cache. Let me know if you're still running into this issue.

This does appear to have been fixed.

Also, can someone attach the V2 label to this issue so it gets some visibility?

I can't do it!

is was a bug in the console page that I've been told has since been fixed. You may need to clear you browser cache. Let me know if you're still runnin

Today i will test again.

I update with the latest version and now works fine. Thank you

Was this page helpful?
0 / 5 - 0 ratings