Skip to content

Experimenting with fronting Neo4J with an LDAP interface using node.js.

License

Notifications You must be signed in to change notification settings

momiller121/cypher2ldap

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

cypher2ldap

Experimenting with fronting Neo4J with an LDAP interface using node.js.

###NOT MUCH TO SEE HERE YET This is all pie in sky at this point - exploration only.

What happens if we wrap neo4j-community-2.1.6 with ldapjs via cypher-stream?

The following assumes that you have neo4j-community-2.1.6 running and one node with a :name attribute.

$ git clone https://github.com/momiller121/cypher2ldap.git
cd cypher2ldap
$ npm install
$ npm start

Nothing but the helloworld for ldapjs wrapped around helloworld for cypher-stream yet...

$ ldapsearch -H ldap://localhost:1389 -x -b o=example objectclass=*
# extended LDIF
#
# LDAPv3
# base with scope subtree
# filter: objectclass=*
# requesting: ALL
#

# example
dn: o=example
objectclass: organization
objectclass: top
o: example
givenName: Mark <--THIS originates from the cypher query

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

About

Experimenting with fronting Neo4J with an LDAP interface using node.js.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published