Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
For a few years we've been doing SAML authentication to Azure AD for Cisco Umbrella. Logins have worked fine through https://login.umbrella.com/sso or the Azure AD URL of https://myapps.microsoft.com/signin/[appId]?tenantId=[ourtenant]. Logged in suc...
We deploy Secure Endpoint 8.1.7 to our few thousand devices, and we started getting a mountain of reports this morning that Google Chrome would not appear on the screen after attempting to open it. It's not 100% across the board, but it is a signific...
A few months back, we deployed Cisco Secure Endpoint 8.0.1 to our pilot Windows group and then our production Windows group. In testing there were seemingly no issues; However, eventually we began to notice that after these upgrades, Windows 10 (most...
We are a hosted Cisco Secure Email customer, and our appliances sit in front of Exchange Online for both inbound and outbound mail. (An Exchange rule + connector sends external mail to Secure Email for outbound delivery)Today I had a complaint of a b...
Our organization (a university in the USA) uses Exchange Online for email, and we have Cisco Secure Email sitting in front of it. All of our mail to external organizations outbounds through Cisco Secure Email via an Exchange Online connector. Secure ...
We see this as well and just have users install both apps. This has been years in process and is quite comical that it's taking so long... Unless I'm missing something. The doc below is from 2020, for reference.https://www.webex.com/content/dam/webex...
This self-resolved sometime today. (12SEP2023) Umbrella' SSO page still redirected to an OpenDNS SSO page at start of business today.. But then SSO to Azure AD began working correctly when I last tried 10 minutes while attempting to get some screensh...
At this point the issue is pretty clear and we're all waiting on Cisco, but I did want to share the following just for historical purposes.Bug ID for this is now customer-visible: https://bst.cisco.com/bugsearch/bug/CSCwf66658Also just got an email a...
Oddly enough, that is working for us too. Agreed that this is a far nicer workaround.TAC gave a soft confirmation of the issue, stating that they're starting to correlate reports of this. They also had me test a fun theory -- If you rename the Chro...
Our test policy where we could reproduce this had the Exploit Prevention engine set to Audit. Once we set that to Disabled instead, the issue was no longer reproducible.Once Exploit Prevention was set back to at least Audit, Chrome stopped working a...
