[mock-orderer] common-root-cas workaround fix#402
Conversation
… right orderer orgs and their root CAs properly. For testing, we initialize the ordererconn with static root CAs from the first organizationMaterials we get which imitate YAMLs. So thats not good, because if we ever set from the yaml and not config-block it will be accepted as long as the service lives. Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
…ns before initializing the connection manager. Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
…testing logic. Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
…ed redundant information. Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
|
This PR is on hold until we make meaningful progress on PR |
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
This PR is now ready for review. |
|
@dean-amar please rebase |
Signed-off-by: Dean Amar <Dean.Amar@ibm.com>
Done. |
liran-funaro
left a comment
There was a problem hiding this comment.
This PR doesn't really removes the common CA paths, it just moves it to another configuration area, disguising it under the organization's root CAs.
In practice, it uses the organizations' root CAs as a the common root CAs.
We should aim to remove the use of the static root CAs.
|
Since this PR and #427 edit some of the same files, and the latter introduces a completely new code architecture, I'll wait for it to be merged. |
|
@dean-amar #427 was merged. You can rebase. |
|
I’m closing this PR. The reason is explained in #339. |
Type of change
Description
Removes the temporary common-ca-cert-paths configuration field and implements proper handling of root CA certificates. Static CA certificates from the initial YAML configuration are now preserved in the ConnectionManager and appended to all organizations' CA certificates during config block updates.
Related issues