Skip to content

Conversation

spencercw
Copy link

AMQP has support for an 'external' authentication scheme which uses some out-of-band method for authenticating the user. For instance, the user may be identified from the Distinguished Name or Common Name in their client certificate. The method by which the user is identified when using external authentication depends on the server configuration.

Add a new 'auth-method' parameter to the amqp destination configuration which may be set to 'plain' or 'external'. When this parameter is omitted or set to 'plain', the existing behaviour is unchanged. When set to 'external' then external authentication is enabled and the username, if supplied, will be used as the identity, although this is generally not needed and may be omitted.

@kira-syslogng
Copy link
Contributor

This user does not have permission to start the build. Can one of the admins verify this patch and start the build?
(admin: you have the next options (make sure you checked the code):
"ok to test" to accept this pull request (and further changes) for testing
"test this please" for a one time test run
do nothing -> CI won't start)

@Kokan
Copy link
Collaborator

Kokan commented Mar 13, 2019

@kira-syslogng ok to test

Copy link
Collaborator

@bazsi bazsi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks pretty good to me, thank you. I had some comments, would appreciate if you could do those yet.

Also do you have a link to amqp documentation where this is explained?

@kira-syslogng
Copy link
Contributor

Build SUCCESS

AMQP has support for an 'external' authentication scheme which uses some
out-of-band method for authenticating the user. For instance, the user
may be identified from the Distinguished Name or Common Name in their
client certificate. The method by which the user is identified when
using external authentication depends on the server configuration.

Add a new 'auth-method' parameter to the amqp destination configuration
which may be set to 'plain' or 'external'. When this parameter is
omitted or set to 'plain', the existing behaviour is unchanged. When set
to 'external' then external authentication is enabled and the username,
if supplied, will be used as the identity, although this is generally
not needed and may be omitted.

Signed-off-by: Chris Spencer <[email protected]>
@kira-syslogng
Copy link
Contributor

Build SUCCESS

@spencercw
Copy link
Author

External authentication is mentioned in the RabbitMQ documentation. I'm having trouble finding anything AMQP-specific so it's possible it's just a RabbitMQ thing.

I have addressed your comments. Thanks.

Copy link
Collaborator

@Kokan Kokan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

Copy link
Collaborator

@gaborznagy gaborznagy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

@gaborznagy gaborznagy merged commit e26a049 into syslog-ng:master Mar 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants