Showing results for 
Search instead for 
Did you mean: 

Head's Up! Site migration is underway. Expect disruption to service on Thursday, Feb. 9!

Neo4j Spring Boot Actuator health and Unsupported authentication token, scheme 'none' is only allowed when auth is disabled

Node Clone

Actuator health endpoint in my Spring boot application shows:

"org.neo4j.driver.exceptions.AuthenticationException: Unsupported authentication token, scheme 'none' is only allowed when auth is disabled."

Neo4j is running, application is working properly. How to properly configure Spring Boot and Actuator to authenticate with Neo4j?



Could you please specify which versions are you using?
The question is based on the fact that there is a Spring Boot auto-configuration provided by Spring Boot 2.4+ but also a Spring Boot Java Driver starter provided by us for Spring Boot versions < 2.4.

Sorry for the late reply. I just noticed your answer.

Spring Boot 2.5.1, Neo4j 4.3

Could you check against the (very simple) example, I have created for differences?

In general there will be only one Java driver bean in the whole application context and used by Spring Data Neo4j AND the actuator.


As I may see, the difference that you are configuring Neo4j via

But in my application I also use LiquiGraph for migrations and my config looks like:

@EnableNeo4jRepositories(basePackages = "com.example.domain.repository.neo4j", transactionManagerRef = "neo4jTransactionManager")
public class Neo4jConfig {

    private String boltServerDatabaseUri;

    private String username;

    private String password;

    public Neo4jTransactionManager transactionManager() {
        return new Neo4jTransactionManager(sessionFactory());

    public SessionFactory sessionFactory() {
        return new SessionFactory(configuration(), "com.decisionwanted.domain.model.neo4j");

    public org.neo4j.ogm.config.Configuration configuration() {

        // @formatter:off
        return new org.neo4j.ogm.config.Configuration.Builder()
                .credentials(username, password)
        // @formatter:on

            prefix = "liquigraph",
            ignoreUnknownFields = false
    public LiquigraphProperties liquigraphProperties() {
        return new LiquigraphProperties();

    public SpringLiquigraph liquigraph(ResourceLoader loader, LiquigraphProperties properties) {
        String jdbcServerDatabaseUri = properties.getUrl();

        final HikariConfig config = new HikariConfig();
        DataSource dataSource = new HikariDataSource(config);

        SpringChangelogLoader changelogLoader = new SpringChangelogLoader(loader);
        return new SpringLiquigraph(dataSource, changelogLoader, properties.getChangeLog(), properties.getExecutionContexts());


You are using Neo4j-OGM here. This is surprising because when using Spring Boot 2.4+ and the Spring Data Neo4j starter, you would get Spring Data Neo4j 6 which is completely independent from Neo4j-OGM.
I suspect that the Spring Data Neo4j (6) related driver got never configured.

yeah... I use SDN5 because failed so far to migrate to SDN6. This is my tech dept for some time in future

Thanks, this helped me. Only difference is I am configuring via application.yml and had to add driver between neo4j and authentication:

      uri: bolt://localhost:7687
        metrics-enabled: true
        username: neo4j
        password: ---


Ok, in this case, you would also have to provide a org.neo4j.driver.Driver bean manually.

public Driver driver(org.neo4j.ogm.config.Configuration configuration) {....}

The auto configuration will, given that a proper Driver is provided, skip the automatic creation part and solely rely on this driver.

Thanks for your answer!

Nodes 2022
NODES 2022, Neo4j Online Education Summit

All the sessions of the conference are now available online