Add username prefix option for IMAP authentication #162
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds another option to IMAP authentication. If configured, this prefix will be prepended to the username before authenticating against an IMAP server.
The prefix is used for authentication only and not part of the Nextcloud username, making it invisible to the end-user.
Use case: Our company's mail provider uses a cryptic prefix for usernames, and there ist nothing we could do about it. For example, a user's mail address would be
[email protected]
, but the IMAP username would be something likegr5418962-username
.To save our users from having to memorize a seemingly random character sequence, this PR allows adding the prefix to the plugin config:
This allows logging in as
username
, which will also be the Nextcloud username. The prefix will never become visible to the user or the application.