Forum Discussion

elijahw's avatar
elijahw
New Contributor
31 days ago

"Sign In With" Provider Not Available

When I add a "Sign in with" option to a login, I can't select any of my existing logins as the correct credentials. I seem to only be offered providers such as Google, Facebook, Twitter/X, etc. For example, Shop (shop.app, also known as Shopify?) is a provider that is linked to many, many stores ... at least in Australia. It's great that I can just sign in with Shop when I'm on a new site and checking out, but I'd like to remember that's how I logged in and 1PW just doesn't allow it.

I see this has been raised before and there's a thank you message from the support staff along with these "ref" numbers, such as:

ref: PB-48105670
ref: PB-48105687

What are these numbers? How can we use them to check up on the status of a request? Google only finds the one specific thread where this number was posted before the conversation was locked so it seems to perhaps just be a number to make people think something is being done when really the request is thrown onto a pile that is never really looked at? 

Any information on how to follow up on these would be helpful, the "Sign in with" feature has been out for a while and people have been requesting this a lot so if it's not even turned up in a beta build, I'm concerned at 1PW's turnaround time for adding an easy feature to their software; even if it's rolled out in two phases where the first is just cosmetic until the second phase actually introduces functions like auto-forwarding and selecting the provider for login etc. Thanks team.

betas
discussion
feature request
vault management

1 Reply

  • CorgiBike's avatar
    CorgiBike
    Occasional Contributor
    29 days ago

    elijahw​ the reference is likely an internal ticketing/documentation system.

    We can’t determine a feature’s ease without knowing their codebase. Assuming they’re like most devs, they likely work in 1-2 week “sprints.” Even if just 4 weeks ago when it was requested, it was prioritized for the next sprint, it’d need internal testing before release and end-user testing. I’ve never seen feature requests for a company this large implemented in less than 3-6 months. We don’t know if it’s a priority.

    I wouldn't expect it is a priority; better to be pleasantly surprised than frustrated.

    A workaround I use is to note the provider in the Notes with a # (enable Markdown).