LogMeIn - Main Page doesn't accept 1PW fill

KBB

Newly upgraded to Lion. 1 PW 3.6.5 (build 31075).



The main page of LogMeIn (www.logmein.com) requests sign-in credentials. I've long been able to use 1 PW to enter this (I've always used the context sensitive right click for the choices - sure will be glad when this is restored ). Since upgrading the sign-on fails and returns another page for credentials. This time 1 PW successfully fills & goes.



Additionally, I've tried removing the login from 1 PW and starting anew in LogMeIn. But, when I enter my credentials, 1 PW doesn't catch it and ask if I want to save it. These entries successfully log in.



I cannot tell if this is a generic problem or something specific to LogMeIn. While not debilitating, this is annoying and not up to 1 PW's usual excellence.



Karl

[Deleted User]

Hi Karl,



Thank you for taking the time to contact us. I'm sorry for the trouble you're experiencing with LogMeIn and our new Safari extension. Because we've been working non-stop to improve things and give our users the best experience we're already a few versions past 3.6.5.



To get this new update please go to 1Password > Check for Updates from within 1Password to get our 1Password 3.7.1 update. Once that's done, please update the Safari extension to the latest version by performing a manual update within Safari > Preferences > Extensions as we detail at the bottom of this guide:



http://help.agilebits.com/1Password3/safari_5.1_install_update.html



With some of the new changes in the update, there are few extra steps to follow. First of all, please go to Help > Troubleshooting > Restart Agent within 1Password and finally restart safari with Command-Option-Q to ensure the extension is properly reloaded.



With the new extension we have a much improved saving system for Logins, so please edit your existing LogMeIn logins and remove their URLs, or delete them if you've made a note of your password. Then go to https://secure.logmein.com/login.asp and enter your e-mail address and password, but don't click 'Log Me In' just yet.



The next step is where the new extension really shines, click the '1P' icon and then click the '+' icon at the top right of the extension to save your details, you can even double-click within the title field to change the name of the Login, and then click 'Save'. That should give you a working LogMeIn login within 1Password on both the main page and login form.



Please let me know how it turns out.







[quote name='KBB' timestamp='1312296692' post='36013']

Newly upgraded to Lion. 1 PW 3.6.5 (build 31075).



The main page of LogMeIn (www.logmein.com) requests sign-in credentials. I've long been able to use 1 PW to enter this (I've always used the context sensitive right click for the choices - sure will be glad when this is restored ). Since upgrading the sign-on fails and returns another page for credentials. This time 1 PW successfully fills & goes.



Additionally, I've tried removing the login from 1 PW and starting anew in LogMeIn. But, when I enter my credentials, 1 PW doesn't catch it and ask if I want to save it. These entries successfully log in.



I cannot tell if this is a generic problem or something specific to LogMeIn. While not debilitating, this is annoying and not up to 1 PW's usual excellence.



Karl

[/quote]

KBB

I followed all of these steps. The outcome is the same. Couple of points:



1. It worked previously (even when I initiated the initial post) at the https://secure.logmein.com/login.asp address. The problem is that prior to Lion, it also worked at www.logmein.com which requests a sign in. Even after updating, the first logmein page still doesn't work. So, while I am able (and somewhat willing) to change the starting point to the address you suggest, I think the behavioral difference in 1 PW is problematic because I have learned to rely on 1 PW to enter credentials when they are requested - not having to know the secret code to get around it or do it twice as is this case.



2. I am disappointed to learn that you think the new way to add to 1 PW (pressing the 1 PW icon, then the + ) is "really shines". It requires non-intuitive action and additional step that the former did not. Previously, 1 PW detected when a new login was present and presented a "save" bar. THAT is elegant and shiny from my perspective.



I am curious why I wasn't alerted to the need to upgrade? I have 1 PW set for automatic checking for newer versions.



For the record: I am a big fan of this product. I count it among the absolute best applications available on a Mac. I continually recommend it to people who ask me what apps they should have. 1 PW is always first on the list. So, I am not trying to be sniggling or regressive. I do like the new interface at the 1 PW button. I do not like at all, the requirement to go there instead of right click, nor to apparently now have to go there to add new logins. I hope you will consider these as you continue to upgrade a really great product.



Karl





[quote name='stu' timestamp='1312306803' post='36072']

Hi Karl,



Thank you for taking the time to contact us. I'm sorry for the trouble you're experiencing with LogMeIn and our new Safari extension. Because we've been working non-stop to improve things and give our users the best experience we're already a few versions past 3.6.5.



To get this new update please go to 1Password > Check for Updates from within 1Password to get our 1Password 3.7.1 update. Once that's done, please update the Safari extension to the latest version by performing a manual update within Safari > Preferences > Extensions as we detail at the bottom of this guide:



http://help.agilebits.com/1Password3/safari_5.1_install_update.html



With some of the new changes in the update, there are few extra steps to follow. First of all, please go to Help > Troubleshooting > Restart Agent within 1Password and finally restart safari with Command-Option-Q to ensure the extension is properly reloaded.



With the new extension we have a much improved saving system for Logins, so please edit your existing LogMeIn logins and remove their URLs, or delete them if you've made a note of your password. Then go to https://secure.logmein.com/login.asp and enter your e-mail address and password, but don't click 'Log Me In' just yet.



The next step is where the new extension really shines, click the '1P' icon and then click the '+' icon at the top right of the extension to save your details, you can even double-click within the title field to change the name of the Login, and then click 'Save'. That should give you a working LogMeIn login within 1Password on both the main page and login form.



Please let me know how it turns out.

[/quote]

KBB

I followed all of these steps. The outcome is the same. Couple of points:



1. It worked previously (even when I initiated the initial post) at the https://secure.logmein.com/login.asp address. The problem is that prior to Lion, it also worked at www.logmein.com which requests a sign in. Even after updating, the first logmein page still doesn't work. So, while I am able (and somewhat willing) to change the starting point to the address you suggest, I think the behavioral difference in 1 PW is problematic because I have learned to rely on 1 PW to enter credentials when they are requested - not having to know the secret code to get around it or do it twice as is this case.



2. I am disappointed to learn that you think the new way to add to 1 PW (pressing the 1 PW icon, then the + ) is "really shines". It requires non-intuitive action and additional step that the former did not. Previously, 1 PW detected when a new login was present and presented a "save" bar. THAT is elegant and shiny from my perspective.



I am curious why I wasn't alerted to the need to upgrade? I have 1 PW set for automatic checking for newer versions.



For the record: I am a big fan of this product. I count it among the absolute best applications available on a Mac. I continually recommend it to people who ask me what apps they should have. 1 PW is always first on the list. So, I am not trying to be sniggling or regressive. I do like the new interface at the 1 PW button. I do not like at all, the requirement to go there instead of right click, nor to apparently now have to go there to add new logins. I hope you will consider these as you continue to upgrade a really great product.



Karl[quote name='stu' timestamp='1312306803' post='36072']

Hi Karl,



Thank you for taking the time to contact us. I'm sorry for the trouble you're experiencing with LogMeIn and our new Safari extension. Because we've been working non-stop to improve things and give our users the best experience we're already a few versions past 3.6.5.



To get this new update please go to 1Password > Check for Updates from within 1Password to get our 1Password 3.7.1 update. Once that's done, please update the Safari extension to the latest version by performing a manual update within Safari > Preferences > Extensions as we detail at the bottom of this guide:



http://help.agilebits.com/1Password3/safari_5.1_install_update.html



With some of the new changes in the update, there are few extra steps to follow. First of all, please go to Help > Troubleshooting > Restart Agent within 1Password and finally restart safari with Command-Option-Q to ensure the extension is properly reloaded.



With the new extension we have a much improved saving system for Logins, so please edit your existing LogMeIn logins and remove their URLs, or delete them if you've made a note of your password. Then go to https://secure.logmein.com/login.asp and enter your e-mail address and password, but don't click 'Log Me In' just yet.



The next step is where the new extension really shines, click the '1P' icon and then click the '+' icon at the top right of the extension to save your details, you can even double-click within the title field to change the name of the Login, and then click 'Save'. That should give you a working LogMeIn login within 1Password on both the main page and login form.



Please let me know how it turns out.

[/quote]

MartyS

[quote name='KBB' timestamp='1312312660' post='36118']

I followed all of these steps. The outcome is the same. Couple of points:



1. It worked previously (even when I initiated the initial post) at the https://secure.logmein.com/login.asp address. The problem is that prior to Lion, it also worked at www.logmein.com which requests a sign in. Even after updating, the first logmein page still doesn't work. So, while I am able (and somewhat willing) to change the starting point to the address you suggest, I think the behavioral difference in 1 PW is problematic because I have learned to rely on 1 PW to enter credentials when they are requested - not having to know the secret code to get around it or do it twice as is this case.



2. I am disappointed to learn that you think the new way to add to 1 PW (pressing the 1 PW icon, then the + ) is "really shines". It requires non-intuitive action and additional step that the former did not. Previously, 1 PW detected when a new login was present and presented a "save" bar. THAT is elegant and shiny from my perspective.



I am curious why I wasn't alerted to the need to upgrade? I have 1 PW set for automatic checking for newer versions.



For the record: I am a big fan of this product. I count it among the absolute best applications available on a Mac. I continually recommend it to people who ask me what apps they should have. 1 PW is always first on the list. So, I am not trying to be sniggling or regressive. I do like the new interface at the 1 PW button. I do not like at all, the requirement to go there instead of right click, nor to apparently now have to go there to add new logins. I hope you will consider these as you continue to upgrade a really great product.



Karl

[/quote]



Thanks, Karl. One of the things that customers are seeing is that in the new Safari extension we have different URL address matching that in previous integrations. It's actually much better than before but it is different. That means that sometimes you'll be on a given web page, ask 1Password to fill the credentials that used to be shown and we say "I'm sorry, there is no match." One way of dealing with that is manual editing of the URL in the Logins item to be one that now matches, and another is to save a new Logins item from this same or a slightly different location. Neither of these are perfect, and have their own merits.



The use of the "+" button is for manually saving a Logins item, not for saving all new Logins. 1Password will still attempt to detect that the web form you've just submitted doesn't have an existing match and offer to save it for you.



As to not being offered an update to the 1Password application itself, I don't know why that didn't happen unless just by chance you had landed on one of the updates that had a broken updater. When things are proper, we'll offer you the latest version that your software license, and operating system will support. So if you are running 1Password on a Leopard system you would not be offered to upgrade to a version that requires Snow Leopard/Lion for instance.



We have lots of work ahead of us, and we love it. These are truly exciting times at AgileBits! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

Kdaniel

I noticed the main question in the thread never got answered.



I'm still having the same problem with 1PASSWORD and LOGMEIN.

It apparently fills in an incorrect pw on the main login page then tells me it's not right on the next page.

When I again refill from 1PW (with no changes to the userid or password in 1PW) on the 2nd page it logs me in correctly.



ALSO it submits the page even if AUTOSUBMIT is turned off and even if NEVER is set for the submit option in 1PW.



Temporary workaround until this somehow gets fixed --- I set the url to be the logged OUT page.



https://secure.logmein.com/loggedout.asp



there it seems to fill the userid and pw correctly.

thightower

[quote name='Kdaniel' timestamp='1323034594' post='54965']

I noticed the main question in the thread never got answered.



I'm still having the same problem with 1PASSWORD and LOGMEIN.

It apparently fills in an incorrect pw on the main login page then tells me it's not right on the next page.

When I again refill from 1PW (with no changes to the userid or password in 1PW) on the 2nd page it logs me in correctly.



ALSO it submits the page even if AUTOSUBMIT is turned off and even if NEVER is set for the submit option in 1PW.



Temporary workaround until this somehow gets fixed --- I set the url to be the logged OUT page.



[url="https://secure.logmein.com/loggedout.asp"]https://secure.logme...m/loggedout.asp[/url]



there it seems to fill the userid and pw correctly.

[/quote]





I also had this issue myself and also got the 2nd submit route. I just tried re saving the login and it now works correctly, could you also try this. I am also using Safari and the 1P extension version 3.8.8

khad

I have never had any trouble using the Login page https://secure.logmein.com/login.asp



Is that not the URL you are using, Kdaniel?