Title: aenglander's Replies | WordPress.org --- # aenglander [ ](https://wordpress.org/support/users/aenglander/) * [Profile](https://wordpress.org/support/users/aenglander/) * [Topics Started](https://wordpress.org/support/users/aenglander/topics/) * [Replies Created](https://wordpress.org/support/users/aenglander/replies/) * [Reviews Written](https://wordpress.org/support/users/aenglander/reviews/) * [Topics Replied To](https://wordpress.org/support/users/aenglander/replied-to/) * [Engagements](https://wordpress.org/support/users/aenglander/engagements/) * [Favorites](https://wordpress.org/support/users/aenglander/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 24 total) 1 [2](https://wordpress.org/support/users/aenglander/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/aenglander/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Proxy Error](https://wordpress.org/support/topic/proxy-error-3/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [8 years, 5 months ago](https://wordpress.org/support/topic/proxy-error-3/#post-9725548) * There are two important details that are required for an authorization response to be received by the LaunchKey WordPress plugin. 1. Your LaunchKey app must be properly configured in the LaunchKey Dashboard. You must set the Callback URL item in the Configuration section of the General tab of you LaunchKey Application settings with the callback URL provided by the plugin during the setup wizard in the _Add this Callback URL to your Application_ or in the plugin settings. 2. The callback URL must be accessible from the LaunchKey servers in the iovation data centers. If you WordPress instance is behind a firewall and cannot be accessed via the Internet, you will not be able to use the LaunchKey plugin. If you are just test driving LaunchKey on your own computer, you can use a reverse proxy tool like Ngrok. * Feel free to respond if this does not resolve your issue. * Adam * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] geofencing login](https://wordpress.org/support/topic/geofencing-login/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [8 years, 9 months ago](https://wordpress.org/support/topic/geofencing-login/#post-9370478) * I apologize for the delayed response. LaunchKey does geo-fencing based on the GPS coordinates of the device attempting to respond to the authentication request. It does not restrict by IP. You can, however setup a geofence around a company’s locations to restrict access to that actual location. If you really want to restrict by IP address range, that is totally possible with other plugins that modify the .htaccess file. It really depends on how you want to setup the restriction. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[LaunchKey] iPhone App is Faulty](https://wordpress.org/support/topic/iphone-app-is-faulty/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/iphone-app-is-faulty/#post-8963161) * The latest release has been updated to properly constrain for that screen size. We will be publishing the release tomorrow and hope to have the release by Friday. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/3/#post-8963045) * The page should have the “launchkey-login.js” file loaded in the footer. That JS should handle removing the password field as long as the ID of the password field has the default value of “user_pass”. You may want to check the JS console in the browser to see if the script is raising errors. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/2/#post-8963019) * I’m not sure what you are asking. The password field is removed when the LaunchKey plugin is active. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/2/#post-8962990) * Awesome, glad to hear it. Sorry about all of the difficulty. I will mark this ticket as resolved. Please let us know if you have any other issues. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/2/#post-8962602) * I am assuming you have hit a known issue with WordPress 4.7. We have a release that has not been promoted to stable as it has not completely finished QA. It will likely resolve the issue you are encountering. It is likely that you will have to reinstall the LaunchKey plugin to update with a zip file. Here is a link to that release zip file: [https://downloads.wordpress.org/plugin/launchkey.1.4.5.zip](https://downloads.wordpress.org/plugin/launchkey.1.4.5.zip). It should be upgraded to stable in the next couple of days as it completes the QA process. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/2/#post-8961866) * I would put the password back with a password reset, log in as the user, and verify the link in the user’s profile. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/2/#post-8961674) * The password field is empty will occur when either: - you are not logging in with valid WordPress username - you are not logging in with valid WordPress username and that user has not been linked to a LaunchKey account * The error occurs when the LaunchKey plugin either cannot find the user or cannot determine the LaunchKey username associated with that user account. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/page/2/#post-8961620) * You need to login with your WordPress user name not your LaunchKey user name. The account also needs to have been linked via the user profile in WordPress. Please log in with your password and verify the WordPress account is linked. If not link the WordPress account with the appropriate WordPress account at that screen. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/#post-8961528) * It should not require any more setup for your account. The other users will need to link their WordPress account with their LaunchKey account. Which version of WordPress are you using? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/#post-8958435) * Okay, this is a bad error message for a fairly uncommon event. 50405 means that your device tokens are out of sync with the API. To prevent an attacker from being able to clone your device and authorize as your device. The device tokens can also get out of sync when network errors occur as you experienced earlier. This issue can be solved one of two ways. 1) Uninstall the application and re- install. 2) Unlink the device from the Unlink screen on any device linked with your user account and then link the device again. Number 2 is a much cleaner way of executing the process but number 1 tends to be easier. * I have identified some long API response times during the time you mentioned and will have our network services team investigate further. tHank you for reporting the issue. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/#post-8958386) * I apologize for the difficulty you are having. There is a known issue with Easy Setup and it will be deprecated in the upcoming release this week. I reviewed our monitoring and log systems and cannot find any instance of down time in that time span. Could you please elaborate on your experience of not being able to log in so that I can research further. Did you attempt to login to Dashboard, [https://dashboard.launchkey.com](https://dashboard.launchkey.com)? Where in the process did it fail, could not submit form on Dashboard, did not get authorization request on mobile device, could not respond to request on mobile device, responded to request but the Dashboard never logged in? * In response to your earlier question, we will not successfully make a callback to a site without a valid certificate. Unfortunately, that would allow for man in the middle attacks against our customers. If your browser requires a your to manually accept the certificate as trusted, our system will not be able to complete the webhook callback to inform your plugin of the user’s response to an authorization request. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LaunchKey] Verification Forever](https://wordpress.org/support/topic/verification-forever/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 1 month ago](https://wordpress.org/support/topic/verification-forever/#post-8956377) * The LaunchKey API calls out on port 443 to api.launchkey.com and back on the port associated to the URL you specified for the callback URL in the LaunchKey Dashboard. * Are you using Easy Setup or the configuration Wizard? * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[LaunchKey] iPhone App is Faulty](https://wordpress.org/support/topic/iphone-app-is-faulty/) * Plugin Author [aenglander](https://wordpress.org/support/users/aenglander/) * (@aenglander) * [9 years, 2 months ago](https://wordpress.org/support/topic/iphone-app-is-faulty/#post-8890646) * We have recreated the issue on our side. It is related to constraints for the iPhone 4 screen size. We may be able to fit it into our scheduled release next week. If not, the fix will be in the following iOS release. If you have any other questions or comments, please feel free to respond. Viewing 15 replies - 1 through 15 (of 24 total) 1 [2](https://wordpress.org/support/users/aenglander/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/aenglander/replies/page/2/?output_format=md)