Issue metadata
Sign in to add a comment
|
alexa.amazon.com Signin fails with Authority_Invalid in M65, OK in M64
Reported by
larrylac...@yahoo.com,
Feb 16 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.73 Safari/537.36 Example URL: alexa.amazon.com Steps to reproduce the problem: 1. Start with a session that's not signed in to Amazon. You'll need a valid amazon id and password 2. Go alexa.amazon.com, fillin the signin form with id, password, click Signin 3. Get a Connection Not Private Cert_Authority_Invalid error What is the expected behavior? Signin OK, goes to Alexa app page What went wrong? Signin fails with Authority_Invalid See comments below Did this work before? Yes 64.0.3282.140 Chrome version: 65.0.3325.73 Channel: beta OS Version: 10.0 Flash Version: The problem started with Windows beta 65.0.3325.51, I didn't catch it until 65..73. The latest M64 I have available is 64.0.3281.140. It works fine there (mostly). If you start with signin at amazon.com (in M65) and then go to alexa.amazon.com, alexa accepts the amazon signin, you get to the Alexa App page, but the app is reported offline. Alexa signout fails with Authority_Invalid. Alexa and amazon use different certs (pitangui.com and www.amazon.com) but the transition between them works OK in M64, bails in M65. The alexa.amazon.com startup redirs to amazon.com for signin - OK in M64. TBD if this is an alexa-cert, M65 conflict. E.g. there are cert validations changes coming in M66 for Symantec distrust, maybe M65 got tighter too. Since access to the Alexa app page is OK when starting with an Amazon signin, it's unlikely this is an Alexa (pitangui) cert problem, since the Alexa page does render OK in some cases. There is also a minor UI problem on the Alexa signin page. The Show Password option stopped working after M63. The box is checked but the password is not displayed. In M63 it shows as a inserted field below password.
,
Feb 18 2018
,
Feb 18 2018
Retract: I can no longer repro the Alexa signin/out error in 65..51 or 65..73. I spent many hours yesterday Sa 2/17 debugging Alexa dot reset issues with Edge (on Amazon acct#2) and in the process rebooted my WiFi router several times, but not my laptop. Today the signin/out error is not reproducible from either Amazon acct#1(me) or acct#2(client), in either 65..51 or 65..73 as it was on Friday 2/17. I suspect the repair came from the WiFi reboot. I don't believe there have been any changes on the Amazon acct#1 in the last 48 hours, although it does get used with other Amazon services (FireStick). I might have also been able to resolve the problem by restarting my laptop, but didn't try that. My bad..
,
Feb 18 2018
Ooops the retract is only partial - The failure is still a problem for the M65 transition. I restarted my chrome many times with M63, M64 and M65 while isolating the problem (2/17), which is all that stable client/user update requires. If the M65 update additionally requires a laptop or WiFi restart for an effective install, that's still a problem. Sorry, I've lost the ability to retest the problem at this site. I can post my crib notes if needed. I'll be at another site Th 2/22 and will retest with a different WiFi router.
,
Feb 18 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by larrylac...@yahoo.com
, Feb 17 2018