Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Provision aliases for provisioned accounts from the user's additional email addresses, instead of only from LDAP

Open
  • Is something wrong?
#13,808 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, php
Domain
full-stack

Research direction

Read AliasSettings.vue and Provisioning\Manager::provisionSingleUser() first to understand the current alias controls and provisioning lifecycle. Trace how ldapAliasesIntegration() supplies aliases and how deleteOrphanedAliases() handles them. Done means a provisioning configuration can use the account’s additional_mail addresses, restricted to its domain, without those aliases being removed on later provisioning requests.

Written by the indexing model from the issue text.

Description

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

With account provisioning, users can only send from an alias address if the user comes from the LDAP backend. For any other backend (user_oidc, user_saml, local users) there is no way to give a provisioned account an alias:

  • the "Add alias" button is hidden for provisioned accounts (AliasSettings.vue)
  • Provisioning\Manager::provisionSingleUser() deletes every alias of the account that is not in the provisioning's alias list on each request (deleteOrphanedAliases()), and that list is only filled by ldapAliasesIntegration(), so it is always empty for non-LDAP users

So an organisation that signs users in through OIDC cannot let them send from shared addresses such as info@ in Mail, although the mail server accepts it.

Describe the solution you'd like

An option in the provisioning configuration, next to "LDAP aliases", to provision aliases from the user's Nextcloud additional email addresses (account property additional_mail, settable by admins through the provisioning API), limited to the configuration's domain. The same addresses already make the calendar treat invitations to them as the user's (they are part of the principal's alternate-URI-set), so one list would serve sending and invitations alike.

This also keeps provisioned accounts ephemeral, the concern raised in #4964: the aliases come from a source the admin controls, so unprovisioning and provisioning again restores them.

Describe alternatives you've considered
  • A static list of aliases per provisioning configuration: does not fit per-user aliases
  • Letting users add aliases to provisioned accounts themselves: the provisioning removes them again on the next request
  • Running a second user backend (LDAP) only to carry the alias attribute
Additional context

Mail 5.12.3, Nextcloud 34.0.3, user_oidc 8.11.0, provisioning with a master password and master user.

Related: #4964 (user-editable aliases for provisioned accounts; this proposal is the admin-side counterpart), #5797 (the same request for the SQL raw backend, closed for low traffic), #5173 and #5198 (LDAP alias provisioning), #13807 (another gap for provisioned accounts with OIDC sign-in).

Dominant language
JavaScript
Stars
1k
Forks
363
Avg merge
1d 10h
Merged PRs (30d)
80

Getting set up

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.

More from nextcloud/mail

All issues in nextcloud/mail

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.