I'm the only one to have this problem? So maybe this means I'm doing something wrong?
I'm trying to expose some RESTful services, which in the backend use an OrientDB database. Since the service is stateless, I wanted to use the token as user identifier, and leave to the DB the access control. Is there any alternative? On Tuesday, August 23, 2016 at 2:59:22 PM UTC+2, Maverick wrote: > > I'm using v.2.0.5 and when I try to open a database with the "remote" > protocol it gives this error: Cannot use a token open on remote database > > Is there any plan to support tokens also on remote databases? > > Is there any workaround? > > Thanks > -- --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
