Page MenuHomePhabricator

[SUGGESTION] Allow existing users to log in with name/password, new users must use OpenID
Closed, DeclinedPublicFeature


Author: amelia.ireland

Allow existing users to log in with their name/password, but force new users to create an account using OpenID.

Setting $wgOpenIDLoginOnly = false still allows account creation without OpenID, but setting $wgGroupPermissions['*']['createaccount'] = false (prevents users creating accounts) stops new users from creating new IDs.

Version: unspecified
Severity: enhancement
See Also:



Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:55 AM
bzimport set Reference to bz51331.

originally proposed in .

Proposal may be difficult to implement, or even impossible.

An according info or warning can only be shown during the account creation phase.

So standard links

  • "login / create an account" and
  • "login / create an account with OpenID"

must be changed to something like

  • "login with username/password (old users)" and
  • "login with OpenID (new users) / create an account with OpenID".

i.e. the only required changes for the present case are

  • password-based account creation must be disabled
  • choose correct message text for password-based login link (with "create account"

This feature was working in earlier versions (of Mediawiki or the extension).

We altered the loginprompt message to:
<span style="background:lightgreen;">Please use the OpenID link to register a new account:</span> <span class="plainlinks OpenID">[ OpenID]</span> You must have cookies enabled to log in to {{SITENAME}}.

So, with $wgGroupPermissions['*']['createaccount'] = false ,
the standard links are

  • Log in
  • Log in / create account with OpenID

OpenID users seemed to recognize their link or found it with no complaints.

@Ryan, Chris, other reporters:

THIS is what you wanted. My invitation to code-review:

Code is live on .

Special:Version should show you "4.00 20131115"

Please test.
Please code-review.

THIS BUG 51331 is not fully solved by that commit, as it requires additional logic to decided between "old" users and "recent" users. My commit howver prepares this step by introcuding more fine-grained openid-user rights, which then can be the base for implementing exactly what you proposed.

Aklapper subscribed.

[Resetting task assignee to avoid cookie-licking. Please reclaim the task when you plan to actively work on this task. Thanks!]

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:13 AM