At this point, I don't anticipate this ever coming upstream. This is probably a good candidate for third-party maintenance after T5055.

sure.

Should I file a separate task for the general feature request?

That feature exists, but it's currently only supported for the Phabricator provider. There's no technical reason we can't support it on other providers, it was just built very narrowly for a Phacility (SAAS) use case and it was simpler to keep it narrowly scoped:

Unsure if fits into this task or not but with only a single auth provider enabled for login it would be nice if it were transparent (and got automatically selected) rather than requiring the user to press a button.

These now show hovercards, which will show project information after M1455 is implemented. I'm just going to close this in favor of T10054, which is an umbrella task tracking related work.

I don't have any current plans to pursue this, per se, in the upstream.

Hi guys. Unfortunately, my organization is no longer using phabricator, so I'm not really able to maintain libphremoteuser at this time.

AFAIK, it is still the only way to this. I added some bits to it to automatically populate email and name when registering, for the case where authentication is done against an ActiveDirectory instance via kerberos and LDAP, which I published at https://github.com/make-all/libphremoteuser

In T814#142452, @craigem wrote:

Is using psigen's libphremoteuser still the only way to achieve this?

There's been no commits to his repo since 2013 and it is broken against current stable Phab.

We should make these show hovercards, which would show project information.