Skip to content

Add multi-tenancy whitelist info. #193

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.

Sign up for GitHub

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
bgravenorst merged 2 commits into from
Feb 24, 2020
Merged

Add multi-tenancy whitelist info. #193

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
09f4d38
Add multi-tenancy whitelist info.
bgravenorst Feb 24, 2020
d55e323
Minor change to kick off Circle CI build.
bgravenorst Feb 24, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/Concepts/Privacy/Multi-Tenancy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,10 @@ owner of the Besu and Orion node.
!!! important
Ensure the multi-tenant Orion node client API is configured to allow access only by the multi-tenant Besu node. Access to your data is secured through Besu using multi-tenancy mode.

If not configured to allow access only by the multi-tenant Besu node, other Orion clients including other Besu nodes may be able to access tenant data.
If not configured to allow access only by the multi-tenant Besu node, other
Orion clients including other Besu nodes may be able to access tenant data.

You can [configure TLS between Besu and Orion](../TLS.md) with the [`whitelist`](https://docs.orion.pegasys.tech/en/latest/Tutorials/TLS/#clientconnectiontlsservertrust) trust mode to secure access.

Multi-tenancy validates that tenants are permitted to use the specified HTTP or
Websocket JSON-RPC requests, and the tenant has access to the requested privacy
Expand Down