NOISSUE - Support disabling Email Agent authentication #1356
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e46b57f to
d6c24f9
Compare
Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com>
Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com>
Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com>
manuio
approved these changes
Feb 8, 2021
fbugarski
pushed a commit
to fbugarski/mainflux
that referenced
this pull request
Mar 8, 2021
* Fix mailer configuration Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Remove unused Driver option Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com> * Add Email Agent README Signed-off-by: dusanb94 <dusan.borovcanin@mainflux.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: dusanb94 dusan.borovcanin@mainflux.com
What does this do?
This pull request adds support for disabling authentication for the Mainflux Email Agent. It also adds support for the
CRAM-MD5authentication method alongside Basic Auth.Which issue(s) does this PR fix/relate to?
There is no such issue.
List any changes that modify/break current functionality
If the username is not present in the agent configuration, no authorization will be used.
Have you included tests for your changes?
No.
Did you document any new/modified functionality?
Yes.