This repository has been archived by the owner on Jan 31, 2023. It is now read-only.
Exported Connection Details include non-enrolled admin identity #596
Assignees
Milestone
Comments
Merged
cazfletch
added a commit
that referenced
this issue
Feb 22, 2019
Enrolled the identity for the gateway view so that exported connection details can be used to create other identities closes #596 Signed-off-by: Caroline Church <caroline.church@uk.ibm.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The wallet that is exported via the 'export connection details', whilst fine for applications that issue transactions, does not contain an admin id that is enrolled with the ca.
Therefore this wallet can't be used to register other identities; within a dev scenario creating additional identities is useful for debugging purposes, and to validate any user checking that might be coded.
The wallet exported is copied from the local wallet that is internal to vsCode. Suggestion therefore that this wallet is created (if it doesn't exist already) by enrolling admin@org1.example.com directly.
Therefore when this is then exported, the dev can create new identities.
The text was updated successfully, but these errors were encountered: