This task is kind of all over the place, but I expect it to be functionally resolved by changes attached to T13244 in service of (internal) PHI774.

Sorry, yeah, I meant T6703.

I believe that instead of T7667 you meant to write T6703.

There are two flavors of this:

This isn't a bug. Here's an example of why the proposed behavior is dangerous:

Ah yes I forgot about the fun of internationalization. Btw those fragments are correct 👍🏻 (I speak Spanish).

Strings with sentence fragments like that can be difficult to translate in the normal human language sense, see:

The translation.override settings seems to be the easiest path forward. I definitely don't want to be modifying the source if I can help it.

This is probably something we'll need in the very long run for T6703 (if we legitimately let you connect to two different LDAP servers, it would be silly to have two "Login with LDAP" dialogs) but, yeah, using translation.override or just editing PhabricatorLDAPAuthProvider might be the shortest path today.

Can you just override the translation? /config/edit/translation.override/

Essentially I would like to customize the "Login or register with LDAP" here to be "Login or register with OpenDirectory"

In T2549#25878, @epriestley wrote:

• I deleted the @mierle account.
• It's currently not possible to link a Phabricator account to more than one external account of a given type (where "type" is one of "Facebook", "Google", "GitHub", etc.). In hindsight this was an architectural mistake, but I didn't think about it at the time and left us with a mess to clean up. It will be resolved by {T1536}, which is a sort of umbrella task for remedying various missteps on the auth pathway. We've made some progress on that, but it will be at least a little while before it lands.

I'm just going to merge this into T5953. The LDAP importer is a contributed patch from yesteryear which we wouldn't bring upstream today, and unlikely to see improvements outside of a more formal upstream effort in T5953.

Phabricator is not an LDAP administration tool and we have no plans to turn it into one.

I think this was building up toward T10939, and the actual solutions we're looking at there probably don't involve this.

In T10621#165969, @epriestley wrote:

How do you imagine Phabricator learning about the existence of new external groups? Just polling a list of every group in LDAP every hour or whatever?

In T10621#165969, @epriestley wrote:

How do you imagine Phabricator learning about the existence of new external groups? Just polling a list of every group in LDAP every hour or whatever?

How do you imagine Phabricator learning about the existence of new external groups? Just polling a list of every group in LDAP every hour or whatever?