This company has a new system and a new login screen to go with it  https://portal.outfox.energy/sign-in

Enpass worked on the old system a few weeks ago

The new screen has 2 fields ... Email ID and Password.  

The Enpass login (I've manually updated the url) doesn't populate either field

I've tried changing the Enpass field name from Username to Email ID (and the Field type) but it did not help.  Enpass ignores the Email ID field in both cases.

 

As for the Password field, Enpass offers to generate a password for me.

 

So, my question is, what would trigger Enpass to recognise the two fields as username and password ?

Presumably it is something about the setup of the web page that Enpass is looking for ... and the web page needs updating

OR is there a way I can get Enpass to work as it is.

I should say that the "Save form" option never appears on the Assistant

 

To work around the autofill issue, you can try using the "Save Webform" feature in the Enpass browser extension. Start by removing any existing login saved for the site. Then, go to the login page, manually enter your email and password, open the Enpass extension, click the three-dot menu, and select "Save Webform." This allows Enpass to capture the exact structure of the login page, which can often resolve issues with sites that use non-standard or dynamic fields.

If that doesn’t help, another option is to manually edit the saved item in Enpass. You can do this by inspecting the login page in your browser (right-click and choose "Inspect") to check the actual name or id attributes used for the input fields. Then, in Enpass, add these as custom fields under the Webform section and save the changes. This manual mapping can help Enpass correctly recognize and autofill the login form.

If the issue continues, feel free to share more details, and we’ll be happy to take a closer look.

I've tried both those things 

 

I mentioned that the "save form" (or "webform") does not appear in the Assistant (or extension)

 

So, the login screen is not being recognised by Enpass

The issue has been escalated to our technical team, and they're currently looking into it. We'll share updates as soon as we have more information.


#SI-4418

Enpass identifies fields by looking at the HTML code of a webpage. If the website uses custom tags or lacks standard "id" and "name" attributes, Enpass may fail to recognize them. Since the "Save form" option is missing, the software cannot manually map these elements. This usually happens when a site is built with modern frameworks that hide traditional input labels. To fix this, you can manually add fields in the Enpass app. Match the field names exactly to the webpage's source code labels. Alternatively, try clicking the Enpass icon inside the browser field to force a manual selection. If the website code remains non-standard, Bazoocam, the developers must update the page to follow basic accessibility rules for password managers to function correctly

@Chang666

Thank you for the response.  I've tried a few things but it seems that only signing in manually works for this site at the moment.

It's not a major problem but if all sites went that way ... it would be !

Happy New Year !

This isn't Enpass; it's on the website.

The email field on the new login page, which uses a contemporary JS form (probably React), does not expose a correct name, id, or autocomplete for password managers. The email box is ignored and "save webform" never appears because Enpass recognizes the password input (hence the generator) but never considers the page to be a legitimate login form.

If the DOM is dynamically hydrated, shadow-DOM, iframe, or non-standard, renaming fields in Enpass won't help. This page lacks the fundamental accessibility semantics that autofill depends on.

In summary, you are not missing anything. Enpass is unable to reliably autofill here until the website corrects its HTML. Currently, the only option is manual login.