Using Never URI for Autofill

[dh024 (David H)]

Yes, exactly. For example, maybe you just wanted to archive and item and never have it match and autofill. Never is essentially a way to exclude a URI from the matching process without having to delete the URI entirely. But if you ever needed it, you could still search for it manually and view it.

[WildWanderer (Justin)]

@dh024

Your screenshot shows that you have multiple URIs entered in the login item that is autofilling. To troubleshoot which one is causing the autofill, set the match option for ALL of them to Never, and then it should no longer autofill. One by one, set each URI back to the original matching rule to figure out which URI is causing the match and autofill.

Good idea. The one causing the interference is Starts with - https://us2.concursolutions.com.

[grb]

@WildWanderer

The one causing the interference is Starts with - https://us2.concursolutions.com.

Evidently, both the admin login screen and the user profile configuration screen have the same host (us2.concursolutions.com). If you go to the two pages, can you see any clear differences in the page URLs, following the host name? If so, you can make the stored URL more specific, to avoid false positive hits when on the user profile page.

[WildWanderer (Justin)]

@grb

If so, you can make the stored URL more specific, to avoid false positive hits when on the user profile page.

This resolved the issue! Since I like having access to my default login while on the site, I added some other Starts with URIs for some of the common pages I visit. Then, I have the Never URI for the user admin page and Starts with for the sign-in pages. I also had to add a custom field for the username on the initial login page since it wasn’t picking that up and kept asking if I wanted to save a new login.

I’ll have to file a feature request for a change to the URI config. What I’d like to see is a NOT operator so I can configure something like this:

*URI 1: Starts with https://us2.concursolutions.com
*NOT URI 2: Exactly https://us2.concursolutions.com/companyadmin/user_detail.asp

So that would have my login available everywhere on the site except the user admin page.

I would also then say to get rid of the Never option and if you want to store a URI that you never do anything with, add it in Notes or as a custom field.

Thoughts?

[WildWanderer (Justin)]

Btw, I didn’t expect to get so much help so quickly. Thank you all for your time! Rockstars.

[grb]

Glad we were able to guide you to a solution.

@WildWanderer

I’ll have to file a feature request for a change to the URI config. What I’d like to see is a NOT operator so I can configure something like this:

*URI 1: Starts with https://us2.concursolutions.com
*NOT URI 2: Exactly https://us2.concursolutions.com/companyadmin/user_detail.asp

So that would have my login available everywhere on the site except the user admin page.

I was thinking along the same lines, but I’m wondering if equivalent funcitonality can be achieved using a regex match?

I would also then say to get rid of the Never option and if you want to store a URI that you never do anything with, add it in Notes or as a custom field.

I have another use case for the Never option.
I have several email accounts that are hosted by tenants of Office365.
Therefore, for these login items, I have set the first URI to https://outlook.office.com, with matching set to Never. This lets me use the “Launch” function to go to the main login page for Outlook webmail, without autofilling anything. I then have other URIs that can autofill the password page, which is specific to each host.