Secure Administration Page
I would like to secure the administration page. I am able to set the login page from http://www.domain.com/Sitefinity to https://www.domain.com/Sitefinity thru IIS. But after login, the https is no longer there. Every pages after login page's url is http://... How do I set all the pages after login to secure pages?
Thanks, ~Pik
Hello Pik Lee,
Thank you for contacting Telerik Support.
Setting SSL for the entire site hasn't been scheduled yet, but here's a quick workaround - you can just provide the ceritficate in IIS and then you have to go and set SSL to each page individually (same goes for backend pages) by going to ~/Sitefinity/Pages or ~Sitefinity/Administration/BackendPages and then click on Actions-> Edit Title and Properties and then form Advanced options tick the Require SSL checkbox.
Greetings,
Boyan Barnev
the Telerik team
I was just looking at this and you can open "title and properties" settings on certain pages, but their titles do not pass the form validation, so you can not click SSL and save the changes.
Considering that all of the connection string info is available through the backend, I can't believe this was not fixed yet... almost a year since 4.x was released.
Additionally, I don't see the login page as one of the pages in the backend editing, so how can I secure this?
Hello Scott Rozman,
Could it be that you are using a version of Sitefinity where we used to have a problem with the Title field not passing the validation. If I remeber correctly, indeed such issue was present, but has been fixed, and I can confirm that there is no problem with this functionality using our latest official release (Sitefinity 4.3). Can you please test this on a newly created project using the latest officially supported version and let me know if any problems persist.
All the best,
Boyan Barnev
the Telerik team
Thanks for the response, Boyan.
I'll have to take your word that this is fixed in 4.3.
I tried upgrading my site to 4.3, but couldn't do so because of a few marketplace items which have not been repackaged for 4.3.
I'm stuck in 4.2.1733 for now.
I spent far too much time the other day trying to keep copies of my project from not upgrading to 4.3, even though I had not clicked "Upgrade" from the Sitefinity Project Manager. The references in my solution were pointing to the _EmptyProject/bin folder to avoid problems when I rebuilt in Visual Studio.... so no messing with 4.3 until I am ready to upgrade for real. Perhaps it is just me, but I found it difficult to have 4.2 and 4.3 living side by side.
If only Sitefinity had a Sitemap Generator, Image Rotator widget and Bread Crumbs widget out of the box!
Hi Scott Rozman,
What you can do is create a binding redirect in your web.config that will make them use the newer version of Telerik.Sitefinity and Telerik.Sitefinity.Model assemblies. Please find below an example of your web.config as it is on my side (I've upgraded from 1650 to 1733, in your case you'll need to specify that the new version is the current version you've upgraded to - I guess if you've moved straight to 4.3 you should use 1873 instead)
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Telerik.Sitefinity" publicKeyToken="b28c218413bdf563" /> <bindingRedirect oldVersion="4.2.1650.0" newVersion="4.2.1733.0"/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Telerik.Sitefinity.Model" publicKeyToken="b28c218413bdf563" /> <bindingRedirect oldVersion="4.2.1650.0" newVersion="4.2.1733.0"/> </dependentAssembly> </assemblyBinding> </runtime>Good day.
I have to use the SSL in some pages inside my application, I used it before in the 4.3 version and it works great, but now when I set the ssl for some page it blows up. I'm having an error that says "Unable to Connect - XXX browser can't establish a connection to the server ". and this only happens with the https pages.
I set up the SSL ports in the web.config, but is not working yet.
As I told you in a last project I used the same configuration and it works without any problem.
Any ideas?
Hi Victor,
Could it be that you have, by any chance, changed the way Sitefinity is set up on your IIS? I'd like to point out that automatic switching to SSL requests will work only if you're using the default http(:80) and https(:443) ports, otherwise if you're moving to a page that requires SSL from an http page, the ports will not be properly handled, and you'll end up with an https request on your http port. We are currently working on implementing the functionality to handle non-default ports, but in the menatime please make sure you are using ports :80 and :443.
Greetings,
Boyan Barnev
the Telerik team