WordPress.org

Ready to get started?Download WordPress

Forums

Social Login
[resolved] Security gets broken in SSL pages and login screen after last plugin update (6 posts)

  1. dKoka
    Member
    Posted 2 years ago #

    Hello,

    After 3.0 update I'm getting security warnings from browser on SSL secured pages and login screen, with the next message in Chrome console window:
    ___
    The page at https://mydomain.api.oneall.com/socialize/login/frame/?
    (...very long text...) ran insecure content from http://public.oneallcdn.com/css/api/socialize/themes/wordpress/default.css.
    ___

    How to get security back to "green" state?

    http://wordpress.org/extend/plugins/oa-social-login/

  2. Claude
    Member
    Plugin Author

    Posted 2 years ago #

    Hello,

    could you post or send us the link to your website?
    http://www.oneall.com/company/contact-us/

    Regards,

  3. Claude
    Member
    Plugin Author

    Posted 2 years ago #

    Ok, found your email.

  4. dKoka
    Member
    Posted 2 years ago #

    Hi Claude,
    the solution you have sent me via e-mail seems to resolve the problem.
    Thank you.

  5. Claude
    Member
    Plugin Author

    Posted 2 years ago #

    Very good.

    Just for completeness:

    dKoka replaced the function oa_social_login_https_o with this code:

    function oa_social_login_https_on()
    {
    	if ( ! empty ($_SERVER ['SERVER_PORT']))
    	{
    		if (trim($_SERVER ['SERVER_PORT']) == '443')
    		{
    			return true;
    		}
    	}
    
    	if ( ! empty ($_SERVER ['HTTP_X_FORWARDED_PROTO']))
    	{
    		if (strtolower(trim($_SERVER ['HTTP_X_FORWARDED_PROTO'])) == 'https')
    		{
    			return true;
    		}
    	}
    
    	if ( ! empty ($_SERVER ['HTTPS']))
    	{
    		if (strtolower(trim($_SERVER ['HTTPS'])) == 'on' OR trim($_SERVER ['HTTPS']) == '1')
    		{
    			return true;
    		}
    	}
    
    	return false;
    }

    We will include this fix in the next version.

  6. Claude
    Member
    Plugin Author

    Posted 2 years ago #

    This bug is fixed in 3.1

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic