-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication issue #16
Comments
@oz123 any idea ? |
Shalom Dror, I think that using Please note, the current logger class re-uses the connection, so make sure you are not creating multiple clients when creating multiple logging handlers (see the tests for that). |
Hi oz, |
What about other kinds of authorization, MongoDB currently supports multiple types, such as certificate based, any plans? |
I don't see any problem adding implementation of certificate based authentication. Would you like to it it too? Thanks for the contributions so far |
Currently, I do not have an enterprise edition either, but it could be provided for development purposes according to their site: It can be split into a different file/test that allow this kind of authentication? |
OK. Then this is feasible. I have no objection for that. I am not in favor for involving docker for testing. |
MongoDB uses the admin database as the default user manager, log4mongo does not support this option.
Another question, why does the connection is not being created with the MongoClient API?
The text was updated successfully, but these errors were encountered: