Skip to content

multi-ingress: Document to disable public account creation #125

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

Merged
supersven merged 2 commits into from
Oct 7, 2026
Merged

multi-ingress: Document to disable public account creation #125

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
935a622
multi-ingress: Document to disable public account creation
supersven Aug 13, 2026
4c37592
Correct description of account registration feature
supersven Oct 7, 2026
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
27 changes: 26 additions & 1 deletion src/how-to/install/multi-ingress.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,25 @@ Multi-ingress configuration settings are discussed in detail in the

Apart from already configured values for domain `green.example.org`, the following changes will be required:

### Brig (optional)

```yaml
brig:
config:
optSettings:
setRestrictUserCreation: true
```

This complements the `FEATURE_ENABLE_ACCOUNT_REGISTRATION: false` setting for
the webapp (see [Instructions for required changes in webapp
values](#instructions-for-required-changes-in-webapp-values)).
`setRestrictUserCreation` prohibits public account creation via API. Creating
users via SCIM or team invitations still works.

N.B. *team owners* are users as well. So, initial team owners must be created
before this setting is activated or these users need to be created via internal
endpoints.

### Galley

```yaml
Expand Down Expand Up @@ -298,7 +317,7 @@ envVars:
ENFORCE_HTTPS: "true"
ENABLE_DYNAMIC_HOSTNAME: "true"
FEATURE_CHECK_CONSENT: "false"
FEATURE_ENABLE_ACCOUNT_REGISTRATION: "true"
FEATURE_ENABLE_ACCOUNT_REGISTRATION: "false"
FEATURE_ENABLE_DEBUG: "false"
FEATURE_ENABLE_FEDERATION: "false" # multi-ingress is not compatible with federation
FEATURE_ENABLE_SSO: "true" # set to "false" if SSO is not used
Expand Down Expand Up @@ -326,6 +345,12 @@ envVars:

Also ensure that the above environment variables are in sync with [https://github.com/wireapp/wire-server-deploy/blob/master/values/webapp/prod-values.example.yaml](https://github.com/wireapp/wire-server-deploy/blob/master/values/webapp/prod-values.example.yaml) in terms of names.

`FEATURE_ENABLE_ACCOUNT_REGISTRATION` would allow public account registration
for *everyone*. This is usually not desirable for on-prems. Also, this feature
depends on the team settings app, which isn't capable of being used via multiple
ingresses, yet. (It's fine to use it to manage teams via the main-ingress,
though.)

### Deploy webapp helm chart

**Re-deploy** the webapp helm chart as following:
Expand Down
Loading