-
Notifications
You must be signed in to change notification settings - Fork 127
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
Database user credentials not enough to access database #32
Comments
Sorry sinfex but this is not true, this functionality exists since the first version. client = pyorient.OrientDB("localhost", 2424)
cluster_info = client.db_open(
'GratefulDeadConcerts', "admin", "admin"
)
print(cluster_info) [{'name': b'e', 'id': 10}, {'name': b'index', 'id': 1}, {'name': b'orole', 'id': 4}, {'name': b'v', 'id': 9}, {'name': b'ofunction', 'id': 7}, {'name': b'default', 'id': 3}, {'name': b'manindex', 'id': 2}, {'name': b'orids', 'id': 6}, {'name': b'ouser', 'id': 5}, {'name': b'internal', 'id': 0}, {'name': b'followed_by', 'id': 11}, {'name': b'oschedule', 'id': 8}] |
I am sorry, but that does not seem to be true. I have tested it several times with python-3.4.1, orientdb-2.0-m3 and a recently forked version of pyorient. I have just tested it out again just in case, using a different server with a fresh installation of python 2.7.5, orientdb 1.7.10 and pyorient 1.2.1, the result is the same.
Would you please double check? The only two explanations I can come up with for your piece of code working for you apart from me encountering an anomaly is either you have admin:admin defined in your orientdb-server-config.xml or you are issuing client.connect("root", "...") before the call to client.db_open. |
Yes, you're right, i've two root user, root and admin, you can find my server configuration here: But this is the right behaviour of the client, the client can't know the root access credentials.
This is an exception raised by orientDB.
I have to check for this, but i think there is not a solution at the moment. |
I believe that should be possible since console.sh does seem to allow this while using the binary protocol (using "remote" connection mode and not "plocal"):
|
The driver does not allow to open a database without connecting to the server instance using server credentials first.
In other words, ODB console allows to use credentials set as the OUser documents in the DB without using the credentials defined in `orientdb-server-config.xml':
pyorient, on the other hand, does not allow to do so without caling OrientDB.connect() first:
The text was updated successfully, but these errors were encountered: