Add enrollUser files to commercial paper #140
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: NIKHIL E GUPTA <negupta@us.ibm.com>
nikhil550
requested review from
christo4ferris,
denyeart,
harrisob,
jyellick,
lehors,
mastersingh24,
mbwhite and
sstone1
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: NIKHIL E GUPTA negupta@us.ibm.com
Add support for using CAs to enroll an application user to the commercial paper sample. This will allow the sample to use best practices for app development and move samples farther away from cryptogen.
With this change, both the old method of moving files into the wallet and the enrollUser.js files can be used to create the application user. The tutorial documentation can be updated to use the enroll file after this PR is merged. After the doc is updated, the program that creates a user from the file system can be removed. There would be no disruption in the user experience.