tbenyon

Hey @vartolomej,

The plugin doesn’t migrate users automatically. When a user goes to login, it will then try to authenticate them using the external users.

It will then create that user in the WordPress database.

Does this answer your question?

I did Rene – I really appreciate it – thank you very much! 🙂

I promise you it will only go towards the best beer! 🙂

I’ll mark this as resolved for now however I’m sure someone will ask me to re-open this in the future.

Thanks again and good luck with your project,

Tom

Hey Rene (@ketr64),

Glad to hear yours has progressed!

I may make a testing system in the admin area in the future so users can test they are using the correct hash algorithm.

If your hashing system is using something more customised than what the settings page caters for there is a hook that you can use to write custom. More details on this in the FAQ for the plugin but feel free to come back here if you have any questions.

Thanks,

Tom 🙂

SIDE NOTE
I’m sure you have everything in hand but using just sha512 to hash your passwords is not the most secure but you may well be putting in additional steps. Bcrypt is a good way to go as it handles custom salts for each password, slow hashing and future proofing by via rounds. More detail in the Security Notes section on the main pluguin page 🙂

Hey @danilocubrovic,

I just wanted to let you know that I have added your feature request of being able to give custom error messages for the exclude hook.

Now if you return a string the user will be blocked and the string will be used as the error for the user. Heres an example:

function myExlogCustomExcluder($userData) {
    return strtotime($userData['expiry']) < strtotime('now') ? 'Your account has expired' : false;
}
add_filter('exlog_hook_filter_custom_should_exclude', 'myExlogCustomExcluder', 10, 1);

The change is in release 1.11.0.

Thanks,

Tom 🙂

Hey @torrespri and @ketr64,

Just an update to let you know that although I could not replicate this error, I have made a change to the code so that this error cannot happen. The change is released as version 1.11.0.

Could you please let me know if this has resolved your issues?

Thanks for your support,

Tom Benyon 🙂

Hey @johnfields,

Hope you’re well. I’ve just sat down and run the experiment I mentioned above.

I cannot replicate the issue you have mentioned. I’ve got a base install and with the plugin active and working using the base WordPress theme and just this plugin installed I can login in both my standard window and an incognito window. I can then continue to navigate in WordPress with both sessions.

For this reason I believe your issue is not to do with this plugin. For this reason, I’m going to mark this as resolved. However, if you do other tests and you believe this is wrong just message back here with replication steps and I’ll be happy to have a further look. 🙂

After thinking I couldn’t I may have been able to replicate – will keep you posted – I’m continuing to look into this.

Thanks John,

Tom

• This reply was modified 5 years, 6 months ago by tbenyon.
• This reply was modified 5 years, 6 months ago by tbenyon.

Hey @ketr64,

“Notice: Undefined index: required in /var/www/wordpress/wp-content/plugins/external-login/views/form_elements/text_field.php on line 18”

This is just a “notice” it’s not an error as such. It’s basically because I have set true to form items that are required but not set anything for ones that are not. PHP warns you that you’ve not set anything. I will make a change for this in the future to get rid of the notification but it won’t break the functionality.

Also, when I try to login, I have the following error message:
“Error: The indicated user could not be found.” and “Notice: Trying to get property ‘ID’ of non-object in /var/www/wordpress/wp-content/plugins/external-login/login/authenticate.php on line 41” as well as “Notice: Undefined property: WP_Error::$ID in /var/www/wordpress/wp-includes/class-wp-user.php on line 171”

I can add some additional safeguarding to protect this from happening but it seems strange that you’re getting this error on that line of code. I’m curious to know if you’re using a particularly old version of WordPress? Do you know your version?
Could you also advise which version of PHP you are running? I’m just surprised you’re getting this error as it is expected that that line will not always find a user and no one else has ever reported an error getting returned – it normally just indicates to the plugin that it should be creating a new user rather than updating the one that’s already been setup in the WordPress database.

These PHP and WordPress versions should help me replicate this issue locally.

Thanks Rene,

Tom

Hey @johnfields,

Really sorry for the delay in getting back to you work and home life has been busy – sincere apologies.

I would be very surprised if the plugin was changing this functionality in anyway because it just uses the authentication hook to either return a user or an error (if they are not authenticated).

However I am not saying for sure this is the case. I’m going to set some time aside at the weekend to see if I can replicate this. This should be pretty straight forward to see if it is this plugin causing the issue. On my local copy I plan to deactivate the plugin and try and login and then again on a private browser session. I’ll then activate the plugin and try this again.

If you have time to experiment with this before I do I welcome your feedback 🙂

If it is the plugin causing this I will of course delve deeper and find out why this is happening 🙂

Thanks John,

Tom