LastPass compatibility, please!

Your login system confuses LastPass. :-( **Please** just give us a username and password box on one login screen, rather than the multi-step clever login. Manually logging in to LastPass to grab my good quality generated password is a hassle. Thanks!!

Are you referring to the community login or the main techsmith website? It appears that the login to the community is at least somewhat predicated upon being logged in to the main techsmith website, i.e., if I'm already logged in there, it's a single button click to log in here. However, if I am not already logged in there I too have to go through the cumbersome multi-screen selection process. I don't know why they just don't use a single set of credentials for both sites, but it is what it is.

Companies try to get fancy with their login mechanisms, which disrupts password keepers. In this era of ever-increasing password length and complexity requirements, more and more people are using systems like LastPass to keep track of it all.

Tangent: I have one system that I regularly use that has the following password requirements:

1. At least 12 characters in length2. Must include both upper and lower case letters3. Must include at least one number4. Must include at least one special character (non-letter, non-number)5. Must be changed every 6 months6. May not re-use previously used passwords

Seriously? And people are supposed to remember this crud?

Site logins MUST support password keepers like LastPass. The only thing worse than sites that use multi-screen logins are those that embed their logins in Flash.

The problematic login is at screencast.com, and clicking the "Sign In" button in the upper right. That sends me to a completely different page with a big splash graphic plus a right pane that provides one box for me to enter just my email address, followed by a "Next" button to move me on to the next page where I am to similarly enter my password.

I'm not sure what motivates such a design, but from the point of view of a user who has many dozens of passwords and relies on LastPass, this design is nothing but a pain. LastPass can't properly identify those fields and I must manually log in to LastPass, than find my screencast account and re-enter my LastPass password to view and copy the password to the clipboard. I then can paste it in to that second field. Ugh.

If there is something that LastPass is doing incorrectly, or needs to know to support your site, please provide them the documentation so that they can support your system . But a normal 2-box login would be much easier.

I just spent some time logging and out of screencast.com using LastPass in Firefox, Chrome, and MSIE... in short: it's a hot inconsistent mess.

However, I don't think 100% of the fault lies with techsmith. LastPass is doing some wonky things. For example, when I saved one profile (I don't recall which browser I was using), it saved the password in both the username and password fields.

Even when I couldn't get LastPass to fully autofill, I could always use the "Copy username" and "Copy password" functions to be able to log in without resorting to a text editor intermediary like the OP said he had to.

This is all under Win7 Enterprise, if that matters. Firefox 50.1, Chrome 55.0.2883.87 m, IE 11.0.9600.18537.

@UofITaxSchool: Yes, it is inconsistent. Part of the issue may be the multi-domain cases as you alluded to earlier - am logged in to TechSmith or ScreenCast, and does LastPass recognize or even offer the other domain's password? Also, I don't really know if TechSmith's sites are set up that way. It looks like they might be and in which case I should go into LastPass and set them as equivalent. (LastPass Icon > My LastPass Vault > Account Settings > Equivalent Domains tab)

But fundamentally this two-step screen design is the issue.

In my setup "Copy Username" and "Copy Password" require re-entry of my LastPass master password which is a bit simpler now, thanks. Previously I only had it in LastPass as my TechSmith credentials, so it was not offered.

For what it's worth, we won't be moving away from the two-step login process in the foreseeable future. This is because our login system supports more than one type of login and that process allows us to see your email address and redirect you to the proper workflow.

For most users the second step will be to enter your password, but it could also redirect you to Google, Microsoft, Twitter or a login system provided by your employer or educator.

Assuming you're accepting our cookies, you shouldn't always be presented with the first step. Once you've signed into an account, it should continue to appear on your login screen, so you don't need to repeatedly enter your email address, and you'd be able to click and then only provide your password.

So Glenn, can we safely set techsmith.com and screencast.com (and anything else?) as "Equivalent Domains in LastPass? (i.e. they share one set of credentials and it is impossible that they could differ)

If so you should consider providing that info to LastPass so they can include it in their large pre-populated list.

I didn't even know LastPass maintained such a list (I'm a 1Password guy), but that's something we can certainly look into. Although, I'm not sure that it really matters because as of a few months ago, when you click the "Sign in" button on screencast.com you should be redirected to signin.techsmith.com in your browser.

Glenn, the issue arises when people have credentials saved for screencast.com, but when you redirect them to techsmith.com the password manager has no way to know to offer the screencast.com credentials. Seems to me that that redirect is exactly why you should share your equivalent domains with LastPass.

I've looked into the equivalent domains functionality in LastPass and from what I can see there is no way for me to tell LastPass that our domains are equivalent. This appears to be a setting that the user has to provide.

I just wanted to provide an update to this thread. Unfortunately, it's not going to be the news you're looking for, but I'd rather be transparent about it than let the issue continue to linger.

I circled back to this a couple of weeks ago, and I had zero luck improving our login inputs to work with autofill in Last Pass. The problem is that we dynamically change the form (show/hide) lots of different inputs based on how you're signing in and Last Pass seems to want a single username/password input on each page.

I would really like to make this work, but unfortunately it'd be a major overhaul to our signin workflow to make that happen. The sad truth, is that it's not likely that will be a priority soon.

That being said, I'm going to convert this problem into an idea, and if there are enough votes, it would help justify reprioritizing this work.

Sorry for the bad news, we should have deliberately tested this the last time we re-worked the sign-in process and we didn't. That will not happen again.

Techsmith.com is one of a handful of sites I've found where it seems effectively impossible to use a form filler to fill in my username. Lastpass recognizes the site but is unable to fill in the name (it will fill in the password after I manually paste in the name). I also saved my credentials in Google Chrome - it is also unable to fill in the username, either automatically or when I manually ask it to fill.

Please fix this - using a password manager and having unique, random passwords for every website is the single best thing your users can do for their security. I can't imagine you designed the login page intentionally to make it hard to fill (that would be insane), but something you've done is preventing auto-filling by Lastpass and Chrome, and that's bad for your users.

I found a workaround for Lastpass, but just to be really clear - this is not a Lastpass issue, it's a techsmith.com issue. It took some digging in your login form and I found a hack, if not a solution, to make LastPass fill in the email address. However, Chrome and Firefox are still *not* able to fill in.

The problem seems to be <input> tag. It has

name="SignIn.Email"

which I've never seen before, and clearly Chrome, Firefox and Lastpass don't recognize it as a field for logging in. The workaround in Lastpass is to edit the Lastpass entry for techsmith.com - you can do that from your vault. You will probably see two fields called SignUp.Password and SignIn.Password (that's what I have at least). Click Add Form Field and add a field called SignIn.Email and put your Techsmith account name (likely your email address) as the value. Lastpass will fill in the field after that.

Unfortunately, that will only fix things for Lastpass, not for Chrome, Firefox, Roboform, etc. A better solution would be to change the name attribute for the field to be something more standard - email seems to be the most common, but username would also work - that's how it's done on the 5 or 6 sites I just checked. Google and Microsoft use something slightly different, but hey, they're Google and Microsoft.

Change the <input> form to name="email" and it will probably work and should have no impact on whatever your login scheme is. It's just a field name.

If the password field on signin.techsmith.com doesn't auto fill with your password, you may be able to tell LastPass to recheck the page with the hotkey Alt+I (that's an I, not an L). The hotkey can be found in LastPass > Preferences > Hotkeys tab.

This should fill in the password. If it does not, then you can try adding a SignIn.Password field in the advanced options for the site. Here's how I have signin.techsmith.com configured for LastPass:

With this configuration, I'm able to use the Alt+I hotkey to fill in the password field.

Thanks for adding screenshots Dave, but the field that is missing is SignIn.Email - SignIn.Password is the password field on the second step. Since the problem we were all having was not having the email address fill in, people will need to add SignIn.Email.

Incidentally, upon returning, it still doesn't work.Techsmith, you have to accept it. YOUR website authentication is broken. Lastpass is fine. Google Chrome is fine. They work with 99.99% of the authentication schemes on the internet.Just in case I wasn't really clear here - YOUR WEBSITE AUTHENTICATION IS BROKEN.I guess at least it matches the software...