summaryrefslogtreecommitdiff
path: root/scripts/rabbitmqctl
diff options
context:
space:
mode:
authorJean-Sebastien Pedron <jean-sebastien@rabbitmq.com>2014-11-25 19:21:27 +0100
committerJean-Sebastien Pedron <jean-sebastien@rabbitmq.com>2014-11-25 19:21:27 +0100
commit037dca04a8f7f7df2a2c8ba8e8aaf45b444f9004 (patch)
treefc9cecaf2cf62954138d680135b8de707a33f915 /scripts/rabbitmqctl
parent741d0941c3894127463bc28838bdb8c26805bb1f (diff)
downloadrabbitmq-server-git-037dca04a8f7f7df2a2c8ba8e8aaf45b444f9004.tar.gz
Add more properties to the user_authentication_* notifications
Until now, the only property was {name, Username}. The added properties are: o {connection_type, network | direct} o {error, Message} (only if the authentication failed) For network connections, the following informations are added as returned by rabbit_reader:infos/2: o auth_mechanism o host o name (the property is renamed to connection_name to avoid conflict with the username) o peer_cert_issuer o peer_cert_subject o peer_cert_validity o peer_host o peer_port o protocol o ssl o ssl_cipher o ssl_protocol o vhost The notification is sent by rabbit_reader:notify_auth_result/5 and rabbit_direct:notify_auth_result/4, not by rabbit_access_control:check_user_login/2 anymore. This fixes a bug where a "user_authentication_success" event would be sent by rabbit_access_control:check_user_login/2, even if rabbit_reader:auth_phase/2 rejects the user later because the connection isn't on the loopback interface.
Diffstat (limited to 'scripts/rabbitmqctl')
0 files changed, 0 insertions, 0 deletions