Page MenuHomePhabricator

Allow login to be disabled for authentication providers
ClosedPublic

Authored by epriestley on Dec 15 2015, 10:52 PM.
Tags
None
Referenced Files
F19087269: D14794.diff
Wed, Dec 3, 12:10 AM
F19059956: D14794.id35769.diff
Sat, Nov 29, 7:16 AM
F18931623: D14794.id.diff
Nov 10 2025, 3:28 AM
F18919337: D14794.diff
Nov 9 2025, 11:47 AM
F18844517: D14794.id35769.diff
Oct 29 2025, 5:57 AM
F18810158: D14794.id35771.diff
Oct 19 2025, 7:51 PM
F18758142: D14794.id.diff
Oct 5 2025, 8:53 PM
F18744657: D14794.id.diff
Oct 3 2025, 3:45 AM
Subscribers
None

Details

Summary

Fixes T9997. This was in the database since v0, I just never hooked up the UI since it wasn't previously meaningful.

However, it now makes sense to have a provider like Asana with login disabled and use it only for integrations.

Test Plan

Disabled login on a provider, verified it was no longer available for login/registration but still linkable.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Allow login to be disabled for authentication providers.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.

Specifically, per T9997, a use case for this is:

  • You want to require login through Google, or some other provider with strong identity guarantees (e.g., mandatory MFA).
  • You also want integrations with an external OAuth system like Asana or JIRA, or other systems in the future.

This is incidentally convenient for us as Phacility since we want instance users to login through central auth, but the primary use case is a reasonable one in geneal.

chad edited edge metadata.
This revision is now accepted and ready to land.Dec 15 2015, 10:58 PM
This revision was automatically updated to reflect the committed changes.