Chrome 60 won't login to ESA Web UI

[tsilveruits]

After upgrading to Chrome 60, I cannot login to the ESA web UI. Entering the password and pressing Enter or clicking Login, the request is not submitted. I have tried Chromium 60 as well. Just sharing so that others can be aware (hopefully) before they upgrade.

[Michael.Young]

I found this issue to also affects end user quarantine safelist/blocklist management, and the workaround fixes it as well.

However, I cannot see us instructing our diverse population of users to download this as a workaround. It's one thing for our management interface and that limited population, but a whole different thing for thousands of users.

Is there an application side fix in the works?

Thanks

-mike

[dmccabej]

ESA/SMA/WSA side fixes are in the works and being prioritized with urgency. There is no timeline we have available, but you can subscribe to notifications on the bug pages for any future updates.

Thanks!

-Dennis M.

[derekmc]

The defect that you referenced was merged into another defect and closed as a duplicate. The merged defect is marked as "WontFix" citing that it meets the updated specification. "

This is actually now required by the spec: https://xhr.spec.whatwg.org/#the-getallresponseheaders%28%29-method and Chrome was fixed to match the spec

https://bugs.chromium.org/p/chromium/issues/detail?id=749086

Please advise.

[Robert Sherwin]

Won't be fixed in terms of Chrome - however, Cisco side, we do have this in-place for our AsyncOS to handle properly. 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf51219

Fixed in the following versions:
11.0.0-272
10.0.3-004
9.8.1-021
9.1.2-053

[Marvin Rhoads]

I'm seeing the same thing on my ESA when trying to login from Chrome 60. It's running the latest GA code - 10.0.0.3-003.

Firefox 55.0b13 works fine, as does Microsoft Edge and Internet Explorer 11.0.44

[Nicolas Melay]

FWIW, the Yahoo name shows up here because IronPort appliances (ESA/WSA/...) make use of YUI, a Javascript library which originates from Yahoo!

https://yuilibrary.com/

Totally unrelated to your browser extensions or anything.

[Nicolas Melay]

Sorry I replied to your post instead of replying to the thread, forum UI did not make this obious...

[Robert Sherwin]

Workaround posted:

Cisco ESA/SMA Login Workaround

You can download Greasemonkey/Tapermonkey script:

https://gist.github.com/robsherw/24c8d66634e260d00e363537eaa93460/raw/abd9eb3cf96bc87e92a6dbf03c71aa3dc22b1403/Cisco_ESA_SMA_XHR_fix.user.js

Please see the TechNote for full instructions and details!

Cheers,

Robert

[Marvin Rhoads]

Thanks Robert and Libin.

The workaround fixed the issue for me.

Best regards,

- Marvin

[Robert Sherwin]

Aside from the Greasemonkey/Tapermonkey scripts --- we do have a backend script that we can now run on ESA/SMA/WSA to correct the Chrome log-in issues.  You will need to open a support case, provide support access via tunnel to the appliance(s), and Cisco TAC can run the script to correct.  Once the script is run, simply clear the Chrome cache and re-access.

-Robert

[Robert Sherwin]

This is officially corrected w/ our 11.0.0-272 release yesterday.  This is currently a Hot Patch, which does require provisioning.  Release Notes for Asyn cOS 11.0 Hot Patch 2 for Cisco Email Security Appliances

Fixed Issues in 11.0.0-272

[iofractal]

where can I find the download. When in the appliance it says I am up to date with Version: 11.0.0-264

[Libin Varghese]

You could open a request with TAC to get the device provisioned.

Hot patch releases are not provisioned automatically and need to be manually added to the list of available upgrades by TAC.

Regards,

Libin Varghese

[treefiddy]

Invalid Bug ID

Please check the ID and enter again to view accurate results.

[Robert Sherwin]

Which BugID are you having issues viewing?