Skip to content
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

Open
drorasaf opened this issue Jan 25, 2016 · 7 comments
Open

Authentication issue #16

drorasaf opened this issue Jan 25, 2016 · 7 comments

Comments

@drorasaf
Copy link

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?

@char0n
Copy link
Collaborator

char0n commented Jan 25, 2016

@oz123 any idea ?

@oz123
Copy link
Collaborator

oz123 commented Jan 25, 2016

Shalom Dror,
In the past mongodb, did authentication against admin. In the mean while you can really store users and passwords everywhere.

I think that using MongoClient instead of a Connection isn't such a bad idea. Can you make a PR for that?

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).

@drorasaf
Copy link
Author

Hi oz,
I can store passwords and users everywhere, but it creates high maintenance for the DBA.
Just to verify, I will create a PR for MongoClient and the authentication.

@drorasaf
Copy link
Author

What about other kinds of authorization, MongoDB currently supports multiple types, such as certificate based, any plans?

@oz123
Copy link
Collaborator

oz123 commented Jul 20, 2016

I don't see any problem adding implementation of certificate based authentication. Would you like to it it too?
As for LDAP and Kerberos, it's only available in the enterprise version, so I don't see how this can be added by me. Also, even I had an enterprise version, I would not add it in the core because it will mess up testing for other developers. So it means there will be code that can't be tested.

Thanks for the contributions so far

@drorasaf
Copy link
Author

Currently, I do not have an enterprise edition either, but it could be provided for development purposes according to their site:
https://www.mongodb.com/lp/download/mongodb-enterprise.
which means it can be created, further more, it can be created with a relevant docker container to create easy tests, but maybe I made a huge jump:)

It can be split into a different file/test that allow this kind of authentication?

@oz123
Copy link
Collaborator

oz123 commented Jul 21, 2016

OK. Then this is feasible. I have no objection for that. I am not in favor for involving docker for testing.
It's an over kill. This package only depends on mongodb and python so setting up the test environment is not hard.
I think the hardest part will be getting the binaries for the enterprise edition (manual registration and co).

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

No branches or pull requests

3 participants