We're rolling out another improvement to Umbrella: modernized block pages with a cool new look and feel, and improvements in the way block page bypass is laid out for users.
We're letting you know in advance because it's usually endusers that see the block pages first and a change to something they're used to could cause a call to the help desk. But, in this case, our new design is meant to help users understand better what their options are and avoid calls entirely.
What's changing?
There's no change in functionality or loss of functionality. When a website it blocked, you'll still see a block page and any customizations you've added, such as a company logo, will still appear.
Block page bypass is now under by a link that says "Administrative bypass" (previously, it said "Admin"). Expanding it out allows you to enter a username or email for the bypass user or if you have a bypass code, you can also enter it here. The only change is to the look & feel -- it's modernized and additional text to help the user has been added.
We've also improved the diagnostics that appear at the bottom of a block page to give more insight into what happened, when and why.
Here's an example of the new look:
When is this happening?
The changes to the block pages will be rolling out across each of our data centers. Each data center hosts a server that hosts the block pages, so we'll do a group of data centers at a time. The first of these is set to change on Monday August 7th, 2017.
The final data centers are scheduled to change Thursday August 17th, 2017.
It is possible that between the 7th and the 17th, some of your users in one area of the world may receive a slightly different block page appearance than users in another part of the world. The experience of using the block page bypass feature should be the same for both.
If you have any questions about this notification, please reach out to umbrella-support@cisco.com
An example of the improved diagnostics for "test.com", as blocked by a domain list:
Comments
2 comments
The way the login is presented is somewhat dangerous as it may prompt logins from users who don't actually have OpenDNS accounts and think they should login with their @mycompany.com corporate SSO/etc account.
Consider validating the email address is a real OpenDNS user before accepting a password, or allowing customers to only display a bypass code.
Hi there,
The actual login functionality-- in so far as the username fields or bpb fields is concerned-- hasn't changed from the previous version. We'll take your points into consideration for a future version though!
Thanks
Matt
Article is closed for comments.