mwillberg
Forum Replies Created
-
Forum: Plugins
In reply to: [Shibboleth] Account merging with different email addresses gives error(Set thread as resolved)
Forum: Plugins
In reply to: [Shibboleth] Account merging with different email addresses gives errorThis was resolved.
The issue was that the login information was not provided to the server. Adding few debug lines to “shibboleth_authenticate_user()” showed that the authentication was using the email address alone.
Allow Automatic Account Merging
[26-Jan-2021 11:35:11 UTC] [Shibboleth WordPress Plugin Logging] get_user_by login: [26-Jan-2021 11:35:11 UTC] [Shibboleth WordPress Plugin Logging] get_user_by email: [email protected] [26-Jan-2021 11:35:11 UTC] [Shibboleth WordPress Plugin Logging] ERROR: User U123 (ID: 123) failed to automatically merge accounts. Reason: An account already exists with this email.Allow Automatic Account Merging (Bypass Username Management)
[26-Jan-2021 11:37:24 UTC] [Shibboleth WordPress Plugin Logging] get_user_by login: [26-Jan-2021 11:37:24 UTC] [Shibboleth WordPress Plugin Logging] get_user_by email: [email protected] [26-Jan-2021 11:37:24 UTC] [Shibboleth WordPress Plugin Logging] SUCCESS: User U123 (ID: 123) merged accounts automatically. [26-Jan-2021 11:37:24 UTC] [Shibboleth WordPress Plugin Logging] SUCCESS: User U123 (ID: 123) successfully authenticated.When the authentication server was correctly providing the login information everything started to work with “Allow Automatic Account Merging”
[26-Jan-2021 13:46:30 UTC] [Shibboleth WordPress Plugin Logging] get_user_by login: U123 [26-Jan-2021 13:46:30 UTC] [Shibboleth WordPress Plugin Logging] SUCCESS: User U123 (ID: 123) merged accounts automatically. [26-Jan-2021 13:46:30 UTC] [Shibboleth WordPress Plugin Logging] SUCCESS: User U123 (ID: 123) successfully authenticated.Forum: Plugins
In reply to: [WPMU Ldap Authentication] Security, leaks LDAP passwords (with patch)Uh-oh, I forgot that you have to do same for “update_welcome_email” filter, but now I noticed a bug in WP that makes it useless.
https://core.trac.ww.wp.xz.cn/ticket/35858
In this situation it is easier to remove all PASSWORD references in message templates.
I have a bit opposite problem. The warning is the same, but it will not downgrade which I would like to do 😎
Both plugin options AND if plugin is disabled the updater will always update to http://ww.wp.xz.cn/nightly-builds/wordpress-latest.zip
Forum: Plugins
In reply to: [Plugin: Maintenance Mode] 5.2 breaks pluggable function architectureThe documentation even has an example how current_user_can is used properly: