Ah. I have never used said plugin, so I don't really know anything about it. My guess would be that your configuration is off a little bit (for example, I have no idea if both stanzas need to be inside of env or not).<br>
<br>But the documentation does say:<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Check the RabbitMQ logs if things don't seem to be working
properly. Look for log messages containing "rabbit_auth_backend_http
failed".<br></blockquote><br>Best of luck.<br><br>-Alex<br><br><div class="gmail_quote">On Mon, Jul 2, 2012 at 5:22 PM, eleanor <span dir="ltr"><<a href="mailto:evangeline.eleanor@gmail.com" target="_blank">evangeline.eleanor@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yeah, that works fine with internal authentication scheme of rabbitmq.<br>
<br>
But what about <a href="https://github.com/simonmacmullen/rabbitmq-auth-backend-http" target="_blank">https://github.com/simonmacmullen/rabbitmq-auth-backend-http</a><br>
. I've installed the plugin successfully.<br>
<br>
Then I've put the following into ebin/rabbit.app as HTTP README says:<br>
<br>
{application,rabbit,<br>
[{description,"RabbitMQ"},<br>
{id,"RabbitMQ"},<br>
{vsn,"%%VSN%%"},<br>
{modules,<br>
<br>
[app_utils,credit_flow,delegate,delegate_sup,dtree,file_handle_cache,<br>
<br>
gatherer,gen_server2,gm,gm_soak_test,gm_speed_test,gm_tests,lqueue,<br>
<br>
mirrored_supervisor,mirrored_supervisor_tests,mnesia_sync,pg2_fixed,<br>
pg_local,pmon,priority_queue,rabbit,rabbit_access_control,<br>
rabbit_alarm,rabbit_amqqueue,rabbit_amqqueue_process,<br>
rabbit_amqqueue_sup,rabbit_auth_backend,<br>
rabbit_auth_backend_internal,rabbit_auth_mechanism,<br>
rabbit_auth_mechanism_amqplain,rabbit_auth_mechanism_cr_demo,<br>
rabbit_auth_mechanism_plain,rabbit_backing_queue,<br>
rabbit_backing_queue_qc,rabbit_basic,rabbit_binary_generator,<br>
rabbit_binary_parser,rabbit_binding,rabbit_channel,<br>
rabbit_channel_sup,rabbit_channel_sup_sup,rabbit_client_sup,<br>
<br>
rabbit_command_assembler,rabbit_connection_sup,rabbit_control_main,<br>
rabbit_ctl_usage,rabbit_direct,rabbit_disk_monitor,<br>
rabbit_error_logger,rabbit_error_logger_file_h,rabbit_event,<br>
rabbit_exchange,rabbit_exchange_decorator,rabbit_exchange_type,<br>
rabbit_exchange_type_direct,rabbit_exchange_type_fanout,<br>
rabbit_exchange_type_headers,rabbit_exchange_type_invalid,<br>
rabbit_exchange_type_topic,rabbit_file,rabbit_framing,<br>
rabbit_framing_amqp_0_8,rabbit_framing_amqp_0_9_1,rabbit_guid,<br>
rabbit_heartbeat,rabbit_limiter,rabbit_log,rabbit_memory_monitor,<br>
rabbit_mirror_queue_coordinator,rabbit_mirror_queue_master,<br>
rabbit_mirror_queue_misc,rabbit_mirror_queue_slave,<br>
rabbit_mirror_queue_slave_sup,rabbit_misc,rabbit_mnesia,<br>
rabbit_msg_file,rabbit_msg_store,rabbit_msg_store_ets_index,<br>
rabbit_msg_store_gc,rabbit_msg_store_index,rabbit_net,<br>
rabbit_networking,rabbit_node_monitor,rabbit_nodes,<br>
rabbit_parameter_validation,rabbit_plugins,rabbit_plugins_main,<br>
rabbit_plugins_usage,rabbit_policy,rabbit_prelaunch,<br>
rabbit_queue_collector,rabbit_queue_index,rabbit_reader,<br>
rabbit_registry,rabbit_restartable_sup,rabbit_router,<br>
rabbit_runtime_parameter,rabbit_runtime_parameters,<br>
<br>
rabbit_runtime_parameters_test,rabbit_sasl_report_file_h,rabbit_ssl,<br>
rabbit_sup,rabbit_tests,rabbit_tests_event_receiver,rabbit_trace,<br>
rabbit_types,rabbit_upgrade,rabbit_upgrade_functions,<br>
rabbit_variable_queue,rabbit_version,rabbit_vhost,rabbit_writer,<br>
supervisor2,tcp_acceptor,tcp_acceptor_sup,tcp_listener,<br>
tcp_listener_sup,test_sup,vm_memory_monitor,worker_pool,<br>
worker_pool_sup,worker_pool_worker]},<br>
{registered,<br>
[rabbit_amqqueue_sup,rabbit_log,rabbit_node_monitor,rabbit_router,<br>
rabbit_sup,rabbit_tcp_client_sup,rabbit_direct_client_sup]},<br>
{applications,[kernel,stdlib,sasl,mnesia,os_mon]},<br>
{mod,{rabbit,[]}},<br>
{rabbitmq_auth_backend_http,<br>
[{user_path, "<a href="http://127.0.0.1/auth/user" target="_blank">http://127.0.0.1/auth/user</a>"},<br>
{vhost_path, "<a href="http://127.0.0.1/auth/vhost" target="_blank">http://127.0.0.1/auth/vhost</a>"},<br>
{resource_path, "<a href="http://127.0.0.1/auth/resource" target="_blank">http://127.0.0.1/auth/resource</a>"}]},<br>
{env,<br>
[{hipe_compile,false},<br>
{tcp_listeners,[5672]},<br>
{ssl_listeners,[]},<br>
{ssl_options,[]},<br>
{vm_memory_high_watermark,0.4},<br>
{disk_free_limit,1000000000},<br>
{msg_store_index_module,rabbit_msg_store_ets_index},<br>
{backing_queue_module,rabbit_variable_queue},<br>
{frame_max,131072},<br>
{msg_store_file_size_limit,16777216},<br>
{queue_index_max_journal_entries,262144},<br>
{default_user,<<"guest">>},<br>
{default_pass,<<"guest">>},<br>
{default_user_tags,[administrator]},<br>
{default_vhost,<<"/">>},<br>
{default_permissions,[<<".*">>,<<".*">>,<<".*">>]},<br>
{cluster_nodes,[]},<br>
{server_properties,[]},<br>
{collect_statistics,none},<br>
{collect_statistics_interval,5000},<br>
{auth_mechanisms,['PLAIN','AMQPLAIN']},<br>
{auth_backends,[rabbitmq_auth_backend_http]},<br>
{delegate_count,16},<br>
{trace_vhosts,[]},<br>
{log_levels,[{connection,info}]},<br>
{ssl_cert_login_from,distinguished_name},<br>
{tcp_listen_options,<br>
[binary,<br>
{packet,raw},<br>
{reuseaddr,true},<br>
{backlog,128},<br>
{nodelay,true},<br>
{linger,{true,0}},<br>
{exit_on_close,false}]}]}]}.<br>
<br>
<br>
<br>
Notice the:<br>
{rabbit, [{auth_backends, [rabbit_auth_backend_http]}]},<br>
{rabbitmq_auth_backend_http,<br>
[{user_path, "<a href="http://some-server/auth/user" target="_blank">http://some-server/auth/user</a>"},<br>
{vhost_path, "<a href="http://some-server/auth/vhost" target="_blank">http://some-server/auth/vhost</a>"},<br>
{resource_path, "<a href="http://some-server/auth/resource" target="_blank">http://some-server/auth/resource</a>"}]}<br>
<br>
<br>
<br>
The problem is that with the following send.py I cannot login to the<br>
rabbitmq with HTTP server:<br>
#!/usr/bin/env python<br>
import pika<br>
<br>
credentials = pika.PlainCredentials('test', 'test')<br>
params = pika.ConnectionParameters(credentials=credentials,<br>
host="localhost", virtual_host='/')<br>
connection = pika.BlockingConnection(params)<br>
channel = connection.channel()<br>
channel.queue_declare(queue='')<br>
channel.basic_publish(exchange='logs', routing_key='', body='Hello World!')<br>
connection.close()<br>
<br>
<br>
I specified the test:test username and password, since that's what I added<br>
to the django application, which is included as an example to the HTTP<br>
plugin. If I enter the GET request:<br>
<a href="http://127.0.0.1:8000/auth/user?username=test&password=test" target="_blank">http://127.0.0.1:8000/auth/user?username=test&password=test</a><br>
<br>
everything is ok - the user is authenticated.<br>
<br>
But when I try to login with the send.py script, the GET request isn't even<br>
made. Now my question is: how to fix rabbitmq for rabbitmq to start making<br>
GET requests to the http server or how to debug an issue?<br>
<br>
Thank you<br>
<br>
--<br>
View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/How-to-specify-user-pass-tp20479p20525.html" target="_blank">http://rabbitmq.1065348.n5.nabble.com/How-to-specify-user-pass-tp20479p20525.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the RabbitMQ mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>