Bitwarden gets confused over fields on AWS login about clients HOT 21 CLOSED

This is not broken for me, but I have found myself configuring the fields myself:
In Bitwarden you want to configure an extra text field:
Name: account
Value: Whatever your account-id is.

Remember that Bitwarden picks this up from html id and will autofill it.

from clients.

why is this closed if is still happening?

from clients.

We have a dedicated issue going at #1621 if anyone is experiencing further autofill problems that they'd like to report. However, custom fields are likely to be the quickest way to fix it for yourself without waiting for us ;)

from clients.

I just come from lastpass, and I can confirm that it does't work. Bitwarden are able to fill username and password, but it fails doesn't work with the account id. Maybe there is a way to point custom fields that are already supported by bitwarden to unmapped fields on the website?

I tink lastpass does someting similar: it fills the account id field with te title of the credential. It is simple and works fine. Although, it might not work for other websites.

from clients.

This is not broken for me, but I have found myself configuring the fields myself:
In Bitwarden you want to configure an extra text field:
Name: account
Value: Whatever your account-id is.

Remember that Bitwarden picks this up from html id and will autofill it.

Recently switched to Bitwarden and was having the same issue. This resolved it for me. Thanks!

from clients.

What page is this happening on because this one seems to work just fine?

from clients.

https://console.aws.amazon.com/ec2/v2/home?region=us-east-1 I've run into the same issue, and just manually copy the password so far

from clients.

The above link redirects me to this:

https://www.amazon.com/ap/signin?openid.assoc_handle=aws&openid.return_to=https%3A%2F%2Fsignin.aws.amazon.com%2Foauth%3Fresponse_type%3Dcode%26client_id%3Darn%253Aaws%253Aiam%253A%253A015428540659%253Auser%252Fec2%26redirect_uri%3Dhttps%253A%252F%252Fconsole.aws.amazon.com%252Fec2%252Fv2%252Fhome%253Fregion%253Dus-east-1%2526state%253DhashArgs%252523%2526isauthcode%253Dtrue%26noAuthCookie%3Dtrue&openid.mode=checkid_setup&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&action=&disableCorpSignUp=&clientContext=&marketPlaceId=&poolName=&authCookies=&pageId=aws.ssop&siteState=unregistered%2Cen_US&accountStatusPolicy=P1&sso=&openid.pape.preferred_auth_policies=MultifactorPhysical&openid.pape.max_auth_age=120&openid.ns.pape=http%3A%2F%2Fspecs.openid.net%2Fextensions%2Fpape%2F1.0&server=%2Fap%2Fsignin%3Fie%3DUTF8&accountPoolAlias=&forceMobileApp=0&language=en_US&forceMobileLayout=0

Which again seems to autofill just fine for me?

from clients.

Is this not the page you are on?

from clients.

https://console.aws.amazon.com/ redirects me to a page like this

from clients.

I get redirected to the same page Kyle gets redirected to.
Try this link: https://account.signin.aws.amazon.com/console

from clients.

I'm not sure how to get tot hat page @DanCardin . Can you provide a direct link to what you are being redirected to?

from clients.

I found this which looks like your page: https://account.signin.aws.amazon.com/console

But autofill seems to work just fine for me on it?

from clients.

It's not working for me either. Every customer has it's own link to his account. For example:
https://123456789.signin.aws.amazon.com/console

or can have an alias to this account like:

https://customer1.signin.aws.amazon.com/console

When you go to your AWS login, you are redirected to some huge url. But at the end
you have three fields: Account, User Name and Password.

• in account field you put: 123456789 or customer1
• in username field you put: your_username
• in pass: you password of course

When you activate Bitwarden, it messes up these three fields. The correct way would be:

• Account: customer1
• Username: your_username
• Pass: *****

But instead it says:

• Account: account
• Username: customer1
• Pass: *****

This Account and username field get messed up.

from clients.

This appears to be fixed in the current version as of April 5th 2017.

from clients.

It's still very broken in the current release as far as I cant tell. Bitwarden does not differentiate between AWS IAM / AWS root user / Amazon Retail.

from clients.

https://signin.aws.amazon.com/
same here, for root options the password is entered on a separate form, it's not auto identified/filled

from clients.

This is still broken

from clients.

This is not broken for me, but I have found myself configuring the fields myself:
In Bitwarden you want to configure an extra text field:
Name: account
Value: Whatever your account-id is.
Remember that Bitwarden picks this up from html id and will autofill it.

Recently switched to Bitwarden and was having the same issue. This resolved it for me. Thanks!

@dave-michael Thanks! This information helped remedy the issue.

from clients.

@eliykat Ya, custom fields are great and all, except for the fact there isn't a way to reference existing properties of the vault item, I shouldn't have to copy the username or password into the custom fields. Duplication is generally a bad thing, and in this case I think such duplication is very bad. Please consider this issue and feature request

from clients.

@undermark5 We've since implemented that feature, they're called Linked Fields and they're a type of custom field. (they are "linked" to an existing property so you don't have to duplicate it.) See more information here.

EDIT: didn't realise this was an old thread, I got a notification on it for some reason. Oh well, the above might help anyway.

from clients.