processone / processone/ejabberd

mod_register: Deny in-band registration in a consistent way

Open
#4,078 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Kind:Feature
Dominant language
Erlang
Stars
6.7k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.

If access is set to none, in-band registrations are not allowed. But if it is set to an access_rule that denies the access, ejabberd announces IBR as a stream feature and clients receive IBR IQ stanzas even if they are not authenticated: <iq xml:lang='en' from='example.org' type='result' id='1'><query xmlns='jabber:iq:register'><username/><password/><instructions>Choose a username and password to register with this server</instructions></query></iq>

That results in clients displaying an account wizard to users but after sending the completed fields, ejabberd responds with the following: <error type='auth'><forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xml:lang='en' xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'>Access denied by service policy</text></error>

Describe the solution you'd like

A solution could be to deny all unauthenticated actions. I.e., only actions such as password changes or account removals would be allowed after the user logged in. That would be more intuitive to admins. In addition, IBR should not be announced as a stream feature because that confuses clients.

Describe alternatives you've considered

Another solution could be to add explicit options allowing/denying registrations, password changes or account deletions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the mod_register entry point and trace how access set to none differs from an access_rule that denies access. Check when IBR is announced as a stream feature and how unauthenticated registration IQ stanzas are handled. Done means denied unauthenticated actions are treated consistently, while permitted authenticated password changes or account removals still work and IBR is not advertised when registration is denied.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang
Domain
authentication, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.