Page MenuHomePhabricator

Improve auth issues warning in Phacility cluster?
Closed, ResolvedPublic

Description

A little discussion in D11707. I'll do the cleanup I mentioned in a sec.

In the Phacility cluster, we'll currently show this warning on instances, because approvals will be off by default and there will be no email domain restriction. This might be confusing to users. One way to fix this would be to add a new flag to provider configs (similar to the auto-login flag) along the lines of:

  • Private Provider: This authentication provider is private and has access controls. This option silences warnings about authentication being too open, provided all configured providers are private.

I'm not sure if that's clear enough in the general case. It should only be possible to set this flag for LDAP and Phabricator OAuth today (in the future, when GitHub supports GitHub Enterprise, it could also support the flag).

I'm not sure if this is worth the effort, though. We could wait until a user gets confused.

Related Objects

Event Timeline

epriestley raised the priority of this task from to Wishlist.
epriestley updated the task description. (Show Details)
epriestley added a project: Phacility.
epriestley moved this task to v1 Open Beta on the Phacility board.
epriestley added subscribers: epriestley, chad, btrahan.

An alternative would be to have a config option to explicitly disable this warning, since the mess above won't do the right thing for installs where access is controlled by a VPN, but I hate config options.

We could maybe put an option in the Auth application, I guess. Ugh.

epriestley claimed this task.

Let's assume this is good enough until we hear otherwise, I don't have a clean way forward if the text-strenght-reduction was insufficient.