Topic-icon SSL and JFBC

Active Subscriptions:

None
9 years 8 months ago - 9 years 8 months ago #46408 by nyocca
SSL and JFBC was created by nyocca
When logging in in the frontend, I often see a message that warns me that the login form is insecure because it retrieves a resource over http://. I looked as best I could for an answer to this in the forum. I saw a post describing how to tell if the option to encrypt the login was working. It was not working. It was communicating via http://. This is my problem. I also saw a post in 2011 about an intractable situation with LinkedIn that was on LinkedIn's radar at the time, and all of that is certainly dated information today. If the option to encrypt login form does not fix the issue of insecurity, and users seeing that the login is insecure, what is your current recommendation for users of the latest version of JFBC and Joomla?
Last edit: 9 years 8 months ago by nyocca.
The topic has been locked.
Support Specialist
9 years 8 months ago #46410 by alzander
Replied by alzander on topic SSL and JFBC
The setting for Encrypt Login Form in the SCLogin module should work just fine. That setting only pertains to the Joomla login options and has nothing to do with the username/password login only. Social logins will use whatever scheme the current page is loaded over and SSL should work just fine.

Beyond that, can you let me know:
* Where you're seeing the message? Is this in the Javascript console of the browser, or somewhere else?
* When you say "When logging in in the frontend,", do you see this message just during the login process, before you try to login, or after you've successfully logged in?

One way to investigate the issue is simply look at the HTML on the page that is showing the mixed-content message. Then, search for "http://". If you find any images or javascript files loaded over http:// and not https://, that's what's causing the error. Simple links to other pages or even forms *can* have http:// links without causing that warning. It's just the content that's loaded on the current page that will cause the problem.

I hope that helps,
Alex
The topic has been locked.