Skip to content
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

Corrected typo on mediator invitation configuration argument #2365

Merged
merged 1 commit into from
Jul 29, 2023
Merged

Corrected typo on mediator invitation configuration argument #2365

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion Multitenancy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ In multi-tenant mode, ACA-Py still exposes a single endpoint for each transport.
ACA-Py allows messages to be routed through a mediator, and multi-tenancy can be used in combination with external mediators. The following scenarios are possible:

1. The base wallet has a default mediator set that will be used by sub wallets.
- Use `--mediation-invitation` to connect to the mediator, request mediation, and set it as the default mediator
- Use `--mediator-invitation` to connect to the mediator, request mediation, and set it as the default mediator
- Use `default-mediator-id` if you're already connected to the mediator and mediation is granted (e.g. after restart).
- When a sub wallet creates a connection or key it will be registered at the mediator via the base wallet connection. The base wallet will still act as a relay and route the messages to the correct sub wallets.
- Pro: Not every wallet needs to create a connection with the mediator
Expand Down