OUser in multi-user web applications

[Andrey Kovalev]

Was OUser created with a purpose of being used in multi-user web applications?

1. Can I create OUser with Writer role each time a new user is registered? Is it a good practice?
2. In that case do I need to create a db pool for each logged-in user?
3. Is the only way to authorize user in Java is to pass his password as a plain text?

Thanks for your feedback.

[Orientdb starter]

I also have the same question. Unless we have one db user per application user, the oRestricted (document level security) is not that useful.

[Artem Orobets]

Hi guys,

It may be used for such purpose, but in some cases you may meet some issues. And yeah, there is still no a convenient API for that.

We still not decided how to change a design to make that 100% supported, here an issue where a discussion going on.

Best regards,

Artem Orobets

Orient Technologies

the Company behind OrientDB

2014-07-10 12:15 GMT+03:00 Orientdb starter <nira...@gmail.com>:

I also have the same question. Unless we have one db user per application user, the oRestricted (document level security) is not that useful.

--

---
You received this message because you are subscribed to the Google Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Argh Skwidge]

Having read the discussion, it seems that the main issue is session management over the binary protocol, and connection sharing for large numbers of sessions.

I'm thinking that if I am using a plocal connection in an embedded connection these issues don't directly relate to my use model. Assuming I am using an OrientGraph or ODatabaseDocumentTx per thread, is there anything else that might trip me up? Memory constraints perhaps?

[Artem Orobets]

Hi Argh, 

By per thread you meant per request, right?

You should think of how to store credentials to prevent user log in each request.

Best regards,

Artem Orobets

Orient Technologies

the Company behind OrientDB

[Argh Skwidge]

On Friday, 11 July 2014 21:54:44 UTC+12, Artem Orobets wrote:

Hi Argh, 

By per thread you meant per request, right?

Correct.
 

You should think of how to store credentials to prevent user log in each request.

Already done.