Hey Rick,
> I think what I was primarily advocating was implementing an authorization
> plugin without implementing an authentication mechanism.
Yeah, me too. I hadn't thought about authentication when I mentioned OAuth.
> Although I've never worked with it, my read on it is that an OAuth
> auth
Good question.
I think what I was primarily advocating was implementing an authorization
plugin without implementing an authentication mechanism.
Although I've never worked with it, my read on it is that an OAuth
authorization mechanism would allow you to use OpenID authentication.
It looks lik
Hi Rick,
You'd not advocate OAuth?
Jim
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
If I were architecting an authentication and authorization mechanism for
Neo4j REST I would probably look at building an OpenSAML based Service
Provider plugin for the Neo4j webserver.
( In the Identity Management world the Service Provider (SP) takes a look
at your identity, and then grants acces
right now either use a proxy in front
or pull the server project and a simple, two line auth filter in front.
perhaps we should add request-filters as an extension mechanism much like the
unmanaged extensions to the server.
M
Sent from my iBrick4
Am 16.03.2011 um 05:28 schrieb Scott Farrar :
HI,
I'm having a little trouble finding information on how authentication
is handled using neo4j. From what I understand, a standalone
implementation doesn't have this feature. With an embedded solution, I
understand that you can use, for instance, authentication in Rails.
Here's what I'd like to
6 matches
Mail list logo
