tbenyon

That’s awesome Luc.

Sounds like you’ve got it all in hand.

If it all works I’d be grateful if you could write a review or even buy me a beer.

Keep me posted with how you get on!

Thanks,

Tom 😊

Hey @kzkggaara,

Just checking in to see how you got on and if this is resolved for you 🙂

No worries @sohom 🙂

I’ll mark this as resolved for now but let me know if you have any more questions.

Do come back and tell me how you got on.

If the plugin does end up doing what you’re looking for, I’d be really grateful if you could write a review or even buy me a beer.

Thanks again,

Tom

• This reply was modified 6 years ago by tbenyon.

Hey @sohom,

This will mostly do what you’ve said but I’d like to clarify what the plugin does to make sure it meets your needs.

The plugin will treat the user details in the PHP database as the single form of truth. Every time a user logs into the WordPress database, the details from the external database (PHP site in your case) get created / updated in WordPress. You need to have a user in WordPress created for the site to function properly.

If you make changes to a user in WordPress they do not get synchronised back to your PHP database.

I think this meets your needs but let me know if you have any other questions 🙂

Thanks,

Tom

Hey @kzkggaara,

This is very possible for the plugin. For users that have a custom hashing algorithm you can validate the password in your own way.

If you look on the FAQ section on the main page there is a part about custom hooks.

In there I document how to use a custom hash by using the exlog_hook_filter_authenticate_hash filter.

In your case, adding the following block of code to your functions.php file should solve the problem for you…

function myExlogHashAuthenticator($password, $hashFromDatabase, $username, $externalUserData) {
    $generatedHash = sha1(strtoupper($username.":".$password));
    return $hashFromDatabase == $generatedHash;
}
add_filter('exlog_hook_filter_authenticate_hash', 'myExlogHashAuthenticator', 10, 4);

I haven’t tested this, it is just pseudocode but it should give you the basis of what you need.

Do come back and tell me how you got on 🙂

Hey @jeremylopez,

Apologies for the delayed reply. Life has been particularly busy at the moment.

I had no idea it was possible to host a PostGres database on S3? Not sure if you meant something else or you’re going to teach me something 🙂

My hunch is this will be a permissions error with AWS or a missing plugin required on your WordPress server for PostGres.

If you want to do more debugging you can add additional error logs in the database section of the plugin to help find the error for your connection.

Have a look in this file:
…/plugins/external-login/login/db.php

The main function is exlog_auth_query(). You can follow the logic from there and add in additional error logs to spot your problem.

I would like to add a feature where we can turn on verbose logging at some point – when life gets less busy! 😛

Let me know how you get on,

Thanks,

Tom

Hi @samuelskidmore,

Apologies for the delayed response.

This is partially possible with the plugin. The only caution is with your use of the word ‘sync’. It will allow users to login to WordPress with the users in your external database however it will not sync changes made in WordPress back to your database.

Thanks,

Tom

Hi @millesm,

So little of the plugin handles what you need and it’s quite a custom thing you’re looking for. I’d recommend you have read of this article (which is what I based the plugin on).

Yours will be super simple with just a basic API request and can all be handled in one file.

I’ll mark this as resolved for now as this is outside the scope of the plugin and I hope I’ve pointed you in the right direction.

I’d love to hear how you get on, and if you have any more questions feel free to post back here also 🙂

Thanks,

Tom