Skip to content

account-registration: add the informational account-required cap #492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

account-registration: add the informational account-required cap #492

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c23a931
account-registration: add the informational account-required cap
emersion Mar 25, 2022
2db311d
Improve typography
emersion Apr 27, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion extensions/account-registration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ consensus.

This specification uses [standard replies][] framework.

### Capability
### Capabilities

This specification adds the `draft/account-registration` capability, whose
presence signifies that the server accepts the `REGISTER` command.
Expand All @@ -71,6 +71,18 @@ The only defined capability keys so far are:
* `custom-account-name` - if present, the account name can be different
from the user's current nickname

This specification also defines the informational `draft/account-required`
capability. If present, it indicates that the connection to the server cannot
be completed unless the clients authenticates, typically via SASL. Note, the
absence of this capability does not indicate that connection registration can
be completed without authentication; it may be disallowed due to specific
properties of the connection (e.g. an untrustworthy IP address), which will be
indicated instead by `FAIL * ACCOUNT_REQUIRED`. If the capability value
`draft/account-registration=before-connect` is advertised, clients should
respond to both of these conditions by suggesting that the user register an
account. Clients MUST NOT request `draft/account-required`; servers MUST reject
any `CAP REQ` command including this capability.

### Commands

REGISTER <account> {<email> | "*"} <password>
Expand Down