Dynamic Content SSL Settings
Posted by S2C Staff, Last modified by S2C Staff on 26 March 2018 03:06 PM
Dynamic Content, SSL & HTTPS
Service2Client sent out the "What? Not Secure?" notice (copied below) a few months ago. The communication was concerning a new Google mandate for websites with any kind of login box. Google is suggesting aka requiring that these sites have an SSL Certificate and an https connection. Google is also reporting that compliance will give a small boost to your Google listings.
For all Dynamic Content clients, if or when you switch your website to https, you will also need to update the Dynamic Content links used in iframes in your site to https. If you update to https and the Dynamic Content pages are blank, this is the reason.
Fixing it is easy, all you have to do is add an "s" at the end of "http" for all the links used in iframes.Example:
**If you plan to switch your site to https, please forward this email to your IT representative.
Some website may need addition updates on our side. If you still see a blank page after applying the above fix, get help here.
To learn about some great new features that we have added to Dynamic Content click here.
What? Not Secure?
It was secure yesterday?
There is a movement in the Tech world to change how login pages are rated in some of your favorite browsers.
What is the issue?
What is the problem with the login box?
The IT community's conflict is that the browser can see the SSL in the embedded login page/box but it does not show that information to the end user. The browser can also see that the page embedding the login pages/box is not using an SSL.
Because of this, embedded login pages/boxes with SSLs are now caught in the middle of this somewhat controversial movement. Although an embedded login page/box with SSL is secure.
But according to Symantec in 12 months it probably will not matter as Google with try to push the world wide web toward using SSL for all web pages.
Cliff Notes for non-techies
How do I get this warning removed from my website?
1. Get ahead of the curve and Buy an SSL certificate today and have it installed on your website.
2. Remove all iframe embedded login pages/boxes from your website and link to a URL SSL secured login page instead. This option may require custom login pages to be built and it will not meet Google's new SSL request coming in the next 12 months.