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

plus sign in arn got skipped #28

Closed
GitOnion opened this issue Oct 18, 2017 · 2 comments
Closed

plus sign in arn got skipped #28

GitOnion opened this issue Oct 18, 2017 · 2 comments

Comments

@GitOnion
Copy link
Contributor

GitOnion commented Oct 18, 2017

Hi,

We encountered an issue, likely from an awsconsole.js function, advisor.generateReport, that ARN with "+" sign in it (as part of the user's name) got parsed to space in the POST request sent to AWS and returned this error message:

ERROR GenerateServiceLastAccessedDetails arn:aws:iam::123456789012:user/foo+bar. Skipping... {"readyState":4,"responseText":"{\"errors\":[{\"message\":\"ARN arn:aws:iam::123456789012:user/foo bar does not exist.\",\"code\":\"NoSuchEntity\",\"type\":\"Sender\"}]}","responseJSON":{"errors":[{"message":"ARN arn:aws:iam::123456789012:user/foo bar does not exist.","code":"NoSuchEntity","type":"Sender"}]},"status":404,"statusText":"Not Found"}

I think this issue is caused by string parsing at AWS end, but wonder what's your opinion and if you have similar issues. Thanks!

@mcpeak
Copy link
Contributor

mcpeak commented Jan 11, 2018

hey @GitOnion this one slipped through somehow. Did you ever figure out how to work around it?

I agree, this looks like it's failing AWS backend validation.

@mcpeak
Copy link
Contributor

mcpeak commented Feb 5, 2019

Closing old issue.

@mcpeak mcpeak closed this as completed Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants