Configure Neo4j to authenticate users from different OUs using the Active Directory attribute samAccountName

Beginning with Neo4j version 3.2.2, it is possible to authenticate using the Active Directory attribute samAccountName as opposed to the LDAP Display Name attribute. This is described in detail in the following KB article: How do I allow for authentication… Read more →

Explore:  


How do I authenticate with cypher-shell without specifying the username and password on the command line

When using $NEO4J_HOME/bin/cypher-shell at the command line and authentication is enabled via the setting $NEO4J_HOME/conf/neo4j.conf: # Whether requests to Neo4j are authenticated. # To disable authentication, uncomment this line dbms.security.auth_enabled=true a username and password can be provided on the command… Read more →

Explore:  


A lightweight approach to testing the Neo4j REST API with Authentication

This article will show examples of how to test the Neo4j REST API for authentication via: Google Chrome Advanced REST Client Linux curl command The Neo4j REST API describes each of the commands you can submit to the Neo4j server. The example… Read more →

Explore:  


How do I allow for authentication using Active Directory attribute samAccountName

Commencing with Neo4j 3.2.2, it is now possible to authenticate using Active Directory attribute samAccountName as opposed to the LDAP Display Name attribute. The following conf/neo4j.conf parameters must be enabled to use samAccountName. dbms.security.auth_enabled=true dbms.security.auth_provider=ldap dbms.security.ldap.authentication.use_samaccountname=true dbms.security.ldap.host=<the LDAP hostname> dbms.security.ldap.authorization.use_system_account=true… Read more →

Explore: