# Mongo::Auth::Unauthorized: User user is not authorized to access db

**URL:** <https://discuss.elastic.co/t/mongo-auth-unauthorized-user-user-is-not-authorized-to-access-db/94229>\
**Category:** Logstash\
**Created:** [July 23, 2017, 5:38am UTC](https://discuss.elastic.co/t/mongo-auth-unauthorized-user-user-is-not-authorized-to-access-db/94229 "2017-07-23T05:38:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![palmtown](https://avatars.discourse-cdn.com/v4/letter/p/97f17d/32.png) [@palmtown](https://discuss.elastic.co/u/palmtown)\
**Post date:** [July 23, 2017, 5:38am UTC](https://discuss.elastic.co/t/mongo-auth-unauthorized-user-user-is-not-authorized-to-access-db/94229/1 "2017-07-23T05:38:54Z")

</div>

I am using mongodb as an output, however, I continue getting error Mongo::Auth::Unauthorized: User user is not authorized to access db. However, I verified user and pass is correct by connecting directly.

:backtrace=\>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/auth/scram/conversation.rb:445:in `validate!'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/auth/scram/conversation.rb:440:in`validate\_first\_message!'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/auth/scram/conversation.rb:112:in `continue'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/auth/scram.rb:59:in`login'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/connection.rb:64:in `connect!'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/connectable.rb:93:in`ensure\_connected'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/connection.rb:130:in `write'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/connectable.rb:66:in`dispatch'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/loggable.rb:44:in `log'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/loggable.rb:67:in`log\_debug'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/connectable.rb:65:in `dispatch'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/operation/executable.rb:35:in`execute'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/connection\_pool.rb:99:in `with_connection'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/server/context.rb:63:in`with\_connection'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/operation/executable.rb:34:in `execute'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/operation/write/insert.rb:72:in`execute\_write\_command'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/operation/write/insert.rb:62:in `execute'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/mongo-2.0.6/lib/mongo/collection.rb:190:in`insert\_many'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-mongodb-3.1.1/lib/logstash/outputs/mongodb.rb:65:in `register'", "org/jruby/RubyHash.java:1342:in`each'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-mongodb-3.1.1/lib/logstash/outputs/mongodb.rb:63:in `register'", "org/jruby/ext/thread/Mutex.java:149:in`synchronize'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-mongodb-3.1.1/lib/logstash/outputs/mongodb.rb:62:in `register'", "org/jruby/RubyKernel.java:1479:in`loop'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-mongodb-3.1.1/lib/logstash/outputs/mongodb.rb:60:in `register'"]}

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 20, 2017, 5:39am UTC](https://discuss.elastic.co/t/mongo-auth-unauthorized-user-user-is-not-authorized-to-access-db/94229/2 "2017-08-20T05:39:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.