root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Explain why each group uses a dedicated node 

Pair: @kjnilsson.
This commit is contained in:
Michael Klishin 2018-09-12 15:16:23 +02:00
parent d1e8ac6c8e
commit ca3612ba62
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
deps/rabbitmq_trust_store/test/system_SUITE.erl vendored
View File

@ -174,6 +174,12 @@ validation_success_for_AMQP_client(Config) ->
?MODULE, validation_success_for_AMQP_client1, [Config]). ?MODULE, validation_success_for_AMQP_client1, [Config]).
validation_success_for_AMQP_client1(Config) -> validation_success_for_AMQP_client1(Config) ->
%% This test intentionally doesn't whitelist any certificates.
%% Both the client and the server use certificate/key pairs signed by
%% the same root CA. This exercises a verify_fun clause that no ther tests hit.
%% Note that when this test is executed together with the HTTP provider group
%% it runs into unexpected interference and fails, even if TLS app PEM cache is force
%% cleared. That's why originally each group was made to use a separate node.
AuthorityInfo = {Root, _AuthorityKey} = erl_make_certs:make_cert([{key, dsa}]), AuthorityInfo = {Root, _AuthorityKey} = erl_make_certs:make_cert([{key, dsa}]),
{Certificate, Key} = chain(AuthorityInfo), {Certificate, Key} = chain(AuthorityInfo),
{Certificate2, Key2} = chain(AuthorityInfo), {Certificate2, Key2} = chain(AuthorityInfo),