New feature-compatibility with dynamic fields

PLMan

One of Polish Banks changed login system the way that login name field has dynamic ID in HTML code. This paralyzed 1Password. Login page for tests is: https://inteligo.pl/secure

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

AGAlumB

@PLMan: Without a legitimate login I can't test this properly myself, but this may help. While 1Password obviously cannot recognize dynamically changing field names, you might benefit from creating a "generic" (for lack of a better term) login by hand in the main 1Password app itself:

1. Open the main 1Password app
2. Create a new Login item
3. Fill in the username, password, and website fields
4. Save it and try it in the browser

In this case, since 1Password has no information about the page, it won't be trying to fill the form it originally saved even if it changes. It will just do its best to find a username and password field. Period. I've found this to be useful on sites that serve a different page based on the user agent as well (mobile versus desktop, for instance). Let me know if that helps! :)

PLMan

You can use login: 112141745 (it is random one but fits format used by Bank). As it is Bank site it is much better if 1P will manage it fully. Generic login will be phishing prone. By the way after inputing login on second page generated password has constant field name :)

littlebobbytables

Hi @PLMan,

So longer term I do hope we can accommodate this behaviour. It isn't the first site to use dynamically generated field name and IDs so my hope is what we do for the will work here as well. If it does a future version of 1Password will be able to fill.

Now there is a workaround for now although it's not elegant at all. It requires using two Login items, one per page. To give accurate steps though can you say what version of 1Password you are using please.

ref: BRAIN-338

PLMan

I'm using 6.8 BETA-2 (680002)

littlebobbytables

Hello @PLMan,

Excellent.

Can you copy the following to your clipboard please.

{
  "URLs": [
    {
      "overview": {
        "label": "website", 
        "url": "https://inteligo.pl/secure"
      }
    }
  ], 
  "categoryUUID": "001", 
  "createdAt": 1494246176, 
  "details": {
    "backupKeys": [
      "ALKCgRq+IeiXxJeTfJnuZIJs7LqnCmDauNZWqsXXee73zAiOmrXTn6SJLc8hoJrU6L3uSl6ERc7TWE/qfm17nQ=="
    ], 
    "fields": [
      {
        "designation": "username", 
        "name": "client_id_field", 
        "type": "T", 
        "value": "112141745"
      }
    ], 
    "passwordHistory": [
      {
        "time": 1494246714, 
        "value": "password"
      }
    ]
  }, 
  "overview": {
    "ainfo": "112141745", 
    "ps": 0, 
    "title": "Inteligo - username", 
    "url": "https://inteligo.pl/secure"
  }, 
  "sectionName": "I", 
  "updatedAt": 1494246714, 
  "uuid": "0D383EB92A6548CA91862721399566D7"
}

In 1Password you should find you now have a menu option File > New Item from Clipboard, please select it. It will create a new item and you will want to edit the username field so it contains the correct ID.

Please repeat with the following but edit the password.

{
  "URLs": [
    {
      "overview": {
        "label": "website", 
        "url": "https://inteligo.pl/secure"
      }
    }
  ], 
  "categoryUUID": "001", 
  "createdAt": 1494246689, 
  "details": {
    "backupKeys": [
      "ALKCgRq+IeiXxJeTfJnuZIJs7LqnCmDauNZWqsXXee73zAiOmrXTn6SJLc8hoJrU6L3uSl6ERc7TWE/qfm17nQ=="
    ], 
    "fields": [
      {
        "designation": "password", 
        "name": "password_field", 
        "type": "P", 
        "value": "password"
      }
    ]
  }, 
  "overview": {
    "ainfo": "\u2014", 
    "ps": 1, 
    "title": "Inteligo - password", 
    "url": "https://inteligo.pl/secure"
  }, 
  "sectionName": "I", 
  "updatedAt": 1494246689, 
  "uuid": "6F13BFF25E834499A697056FCCA56298"
}

Do you find that if you fill each page with their respective Login item that they both correctly fill?

PLMan

Yes, it works. Waiting for final solution in 1Password.

AGAlumB

Thank for confirming! We'll see what we can do to make 1Password smarter here.