Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
StreamChain Prototype
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
zistvan-public
StreamChain Prototype
Commits
242f56cb
Commit
242f56cb
authored
7 years ago
by
Gari Singh
Committed by
Gerrit Code Review
7 years ago
Browse files
Options
Downloads
Plain Diff
Merge "[FAB-10285] MSP topic"
parents
6528c9db
7fbc87d8
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/source/msp.rst
+2
-2
2 additions, 2 deletions
docs/source/msp.rst
with
2 additions
and
2 deletions
docs/source/msp.rst
+
2
−
2
View file @
242f56cb
...
...
@@ -249,7 +249,7 @@ configuration in commonly met scenarios.
**1) Mapping between organizations/corporations and MSPs**
We recommend that there is a one-to-one mapping between organizations and MSPs.
If a different
mapping
type of mapping is chosen, the following needs to be to
If a different type of mapping is chosen, the following needs to be to
considered:
- **One organization employing various MSPs.** This corresponds to the
...
...
@@ -322,7 +322,7 @@ peer/orderer MSP would be the administrators of that MSP.
Another point to be considered with this approach is that peers
authorize event registration requests based on membership of request
originator within their local MSP. Clearly, since the originator of the
request is a client, the request originator is always d
oo
med to belong
request is a client, the request originator is always d
ee
med to belong
to a different MSP than the requested peer and the peer would reject the
request.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment