Amazon Web Services doesn't log properly
Reported by
pavel.as...@gmail.com,
Jan 15 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Example URL: https://signin.aws.amazon.com/signin?redirect_uri=https%3A%2F%2Fconsole.aws.amazon.com%2Fconsole%2Fhome%3Fstate%3DhashArgs%2523%26isauthcode%3Dtrue&client_id=arn%3Aaws%3Aiam%3A%3A015428540659%3Auser%2Fhomepage&forceMobileApp=0 Steps to reproduce the problem: 1. Enter credentials 2. Try to login 3. Fail What is the expected behavior? successful login What went wrong? Everything. AWS seems to not fetch email properly and treat email field as empty. Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 63.0.3239.132 Channel: stable OS Version: 10.0 Flash Version:
,
Jan 16 2018
pavel.astashonak@ Thanks for the issue. Tried to test this issue on Windows 10 on latest Canary 65.0.3322.3 by creating an account on Amazon Web services, but couldn't create. Request you to please provide us test credentials which will help in further triaging of this issue. Thanks..
,
Jan 16 2018
I'd rather prefer to not to reveal my credentials, as it is private info. Try to create test account on any other browser (Edge or IE) and then try to sing in in Chromium.
,
Jan 16 2018
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 17 2018
pavel.astashonak@ Thanks for the feedback. Retried this issue On windows 10 by creating an account on AWS, but unable to create one as the site is asking for credit card details. As the credentials are not available at TE end to test this issue, adding TE-NeedsTriageFromMTV and requesting someone from MTV team to please look into this issue and help in further triaging. Thanks..
,
May 3 2018
This is not Chrome problem, but problem of one of the extensions. Can be closed.
,
May 3 2018
Closing as per #6 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jan 15 2018