Skip to content

Fix TLS tests in Node #321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 12, 2018
Merged

Fix TLS tests in Node #321

merged 2 commits into from
Jan 12, 2018

Conversation

lutovich
Copy link
Contributor

No description provided.

Couple TLS tests got broken when executed against 3.1 neo4j database,
which generates self-signed certificate for default listen address in
neo4j-server. Default listen address has been changed from IPV4
localhost to IPv6 localhost '::' to verify IPv6 support. This change
made 3.1 database generate self-signed certificate with '::' hostname.
Tests however tried to connect to regular 'bolt://localhost' and
hostname validation failed because they expected 'localhost' but
received certificate with '::'. Starting from 3.2 neo4j generates
self-signed certificates based on the advertised address, which we
do not change for tests and thus it's always 'localhost'.

This commit fixes the problem by adding an explicit listen address for
http with IPv4 localhost and default port 7474 to the neo4j config file.
@lutovich lutovich merged commit 2b27814 into neo4j:1.5 Jan 12, 2018
@lutovich lutovich deleted the 1.5-fix-tls-tests branch January 12, 2018 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant