Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Credentials file download fails with GUID filename #29

Closed
BrandonDusseau opened this issue Feb 18, 2019 · 1 comment
Closed

Credentials file download fails with GUID filename #29

BrandonDusseau opened this issue Feb 18, 2019 · 1 comment

Comments

@BrandonDusseau
Copy link

BrandonDusseau commented Feb 18, 2019

As of this morning, I am no longer able to download the credentials file using the extension. Instead of the file, I now get a failed download with a GUID as a filename.

capture

Debug log below:

script.js:59 DEBUG: onBeforeRequest event hit!
script.js:79 DEBUG: samlXmlDoc:
script.js:80 [redacted]
script.js:120 ApplySessionDuration: false
script.js:121 SessionDuration: null
script.js:122 hasRoleIndex: true
script.js:123 roleIndex: arn:aws:iam::[redacted]
script.js:161 RoleArn: arn:aws:iam::[redacted]
script.js:162 PrincipalArn: arn:aws:iam::[redacted]:saml-provider/[redacted]
script.js:187 DEBUG: Successfully assumed default profile
script.js:188 docContent:
script.js:189 [default]
aws_access_key_id = [redacted]
aws_secret_access_key = [redacted]
aws_session_token = [redacted]
script.js:195 Generate AWS tokens file.
script.js:261 DEBUG: Now going to download credentials file. Document content:
script.js:262 [default]
aws_access_key_id = [redacted]
aws_secret_access_key = [redacted]
aws_session_token = [redacted]
script.js:266 DEBUG: Blob URL:blob:chrome-extension://ekniobabpcnfjgfbphhcolcinmnbehde/b7e150af-9f7a-4bf4-88b7-e8a5859511d7

Attempting to visit the above URL results in a 404.

Settings:
Filename: credentials
Apply SessionDuration: no
Debug logging: yes
ARN list: none

Running on Chrome version 72.0.3626.81 (updates are disabled by group policy)
Extension version: 2.7

@prolane
Copy link
Owner

prolane commented Feb 18, 2019

Thanks for reporting. This is a known bug in Chrome.
See issue #28

You need Chrome 72.0.3626.96 or higher.

You could try the workaround mentioned over here if you are unable to upgrade Chrome:
#28 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants