Ok seems like you have a few moving parts here… You want to add a new meta field (unique code) to the user meta for all users You want to modify the default login form by adding an extra field… a unique code field This unique code field should allow the user to login if … Read more
Yes you can, you can easily just ask for a user name and/or email or text/email them their OTP(one time password). This is becoming more popular on mobile apps that ask for just a phone number and text a code to enter for authentication. Examples https://auth0.com/blog/how-passwordless-authentication-works/ https://www.okta.com/security-blog/2018/04/is-passwordless-authentication-actually-secure/ For wordpress auth there are plugins already. https://wordpress.org/plugins/passwordless-login/
For OpenSSH there is BatchMode, which in addition to disabling password prompting, should disable querying for passphrase(s) for keys. BatchMode If set to “yes”, passphrase/password querying will be disabled. This option is useful in scripts and other batch jobs where no user is present to supply the password. The argument must be “yes” or “no”. … Read more
Authentication is the process of verifying who you are. When you log on to a PC with a user name and password you are authenticating. Authorization is the process of verifying that you have access to something. Gaining access to a resource (e.g. directory on a hard disk) because the permissions configured on it allow … Read more
Try ssh -o PasswordAuthentication=yes -o PreferredAuthentications=keyboard-interactive,password -o PubkeyAuthentication=no host.example.org In ssh v2, keyboard-interactive is another way to say “password”. The -o PubkeyAuthentication=no option instructs the client not to attempt key pair authentication. In addition, the PasswordAuthentication=yes option is to override any previously configured ssh options that may have disabled it.
It is indeed not possible to pass the username and password via query parameters in standard HTTP auth. Instead, you use a special URL format, like this: http://username:[email protected]/ — this sends the credentials in the standard HTTP “Authorization” header. It’s possible that whoever you were speaking to was thinking of a custom module or code … Read more
By default, each time a new hash is generated (e.g. wp_hash_password()) WordPress salts it with random bytes, producing a unique hash for each call. The string returned from wp_hash_password() consists of four parts concatenated in order – the hashing algorithm ID, the exponent of hash iterations, the randomly generated salt, and finally the salted and … Read more
At first glance it looks like you need to POST the token as a ‘jwt’ property in a JSON object, the same way you’d POST it to the validate endpoint: curl -X POST \ http://dev.wordpress/wp-json/aam/v1/refresh-jwt \ -H ‘Content-Type: application/json’ \ -H ‘cache-control: no-cache’ \ -d ‘{ “jwt”: “0yJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE1NDM4OTExNjQsImV4cCI6MTU0Mzk3NzU2NCwidXNlcklkIjoxfQ.0wGIbcTDH5yWSsdStZFct_-auyOFJqf3NKQasTCs4QU” }’ (based on https://forum.aamplugin.com/d/4-how-to-validate-jwt-token) It doesn’t look … Read more
Puuh, after a full day of research in total, I realized the problem.. First of all, the code above is not supposed to work actually. The oauth parameters have to go into the query string apparently. That’s how all WooCommerce client APIs do it: post(endpoint, data_params, params = null) { const method = ‘POST’ const … Read more
In case anyone has issues like I did, I found this discussion where I added the code and instantly was authenticated. Not sure if its a WordPress issue or a PHP one, but I feel that the ANY portion of the WordPress authentication was getting blocked first to find the Proxy type, but timing out. … Read more