Alain-Aymerick FRANCOIS

Hi,

I’ve tested WPS Hide Login without WP Cassify. This plugin is buggy. When i try do access directly to xxxx.com/wp-admin/, it give me a 404 error.

Is your homepage (xxxx.com) protected by authentication or is public page ?

Can you give me more informations when you try to connect to CAS Server ? From wich blog URL ?

Have you tried to build auth button link with shortcode : https://wpcassify.wordpress.com/plugin-shortcodes/

With shortcode you can put your custom login URL to replace standard wp-login.php.

Best regards

Hi,

First of all, please re-post the seconde question in new thread, it would be clearly for another users.

Okay, it’s normal that you’re redirected directly to standard CAS logout page. Probably, you’ve not configured your CAS server with “followServiceRedirects” option.
https://jasig.github.io/cas/4.2.x/installation/Logout-Single-Signout.html

• Deactivate WPS Hide Login plugin
• Configure followServiceRedirects option in your CAS Server. Edit cas.properties file and then put this option to “true” like below.
• Create a public page in your blog where your explain the reason of user logout : You’ve been disconnected because you’ve not local WordPress Account ! Please contact admin@yoursite.edu
• In WP Cassify admin page, in Authorization rules settings panel, put url of public logout page previously created in User not allowed redirect url field
• Update changes

In your cas.properties (On your CAS Server) :
cas.logout.followServiceRedirects=true

NB : If you leave empty User not allowed redirect url option, home_url() is used instead.

Keep me informed if it solved your problem.

Best regards.

Hi,

Thanks for reply. You’re right. I’ve forgotten to pass $wp_cassify_network_activated in init() function of WP_Cassify_Shortcodes class. Then, if you’ve activated plugin on Network, it generate an error.

I’ve corrected the code in version 1.6.6.

Keep me informed if bug is still present in new version.

Best regards.

Hi,

WP Cassify plugin require at least PHP version 5.3.1. See requirement :

• https://fr.wordpress.org/plugins/wp-cassify/
• https://wpcassify.wordpress.com/requirements/

This is because i use php namespaces in my code. Namespaces are only supported from 5.3 :
http://php.net/manual/en/language.namespaces.basics.php.

I would advise you to upgrade your php version. Another reason is for security concerns.

I’m sorry but i can’t adapt my code because this will require a rewrite of all plugin code.

Best regards.

Thanks for your feedback.

Please update to new version 1.5.8 which solve the problem.

Ok, I close the ticket.

Ok, thanks for stacktrace.

Ok, patch the function like this while new version of plugin are being released :

public static function wp_cassify_do_ssl_web_request( $url, $ssl_cipher ) {

if (! function_exists ( ‘curl_init’ ) ) {
die( ‘Please install php cURL library !’);
}

$ch = curl_init();

curl_setopt( $ch, CURLOPT_HEADER, false );
curl_setopt( $ch, CURLOPT_URL, $url ) ;
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, 1 );
curl_setopt( $ch, CURLOPT_SSL_VERIFYHOST, 2);
curl_setopt( $ch, CURLOPT_SSL_VERIFYPEER, 1);

//curl_setopt( $ch, CURLOPT_USERAGENT,’Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13′ );
curl_setopt( $ch, CURLOPT_SSLVERSION, 0 );

if ( ( defined( ‘WP_DEBUG’ ) ) && ( WP_DEBUG == true ) ) {
curl_setopt( $ch, CURLOPT_VERBOSE, true );
}

$response = curl_exec( $ch );

if( curl_errno( $ch ) ) {
if ( ( defined( ‘WP_DEBUG’ ) ) && ( WP_DEBUG == true ) ) {
$info = curl_getinfo( $ch );
die( ‘Curl error: ‘ . curl_error( $ch ) . print_r( $info, TRUE ) );
}
else {
die( ‘Curl error: active WP_DEBUG in wp-config.php’);
}
}

curl_close( $ch );

return $response;
}