.alice.yaml. For the purposes of this example let's also create a second user
.organization-config.yamlwith the content something like the following.
.organization.yamlfile will look something like the following.
statusfield is set to
requestedat this stage, this means our team has been notified of your intent to create the organization and will review and get in contact with you via the email provided. At this stage only you and the team at Meeco can see the organization. You can check organization was created and in requested state waiting for approval with the following command.
@meeco/sdknpm package or hitting our API endpoints directly using the SDK as a guide.
.organization-service-config.yamlsomething like the following. (Hint: you can use the cryppo cli https://github.com/Meeco/cryppo-cli to quickly and easily create a keypair with the command
cryppo genkeypair -p private.pem -P public.pem).
.organization-service.yamlshould have output like the following.
metadata.privateKeyhere should be saved as configuration for your organization service application.
.organization-service-auth.yamlshould look like the following.
metadata.vault_access_tokenshould be saved as configuration for your organization service application. So from now your application has a
private_key, these should be set as configuration variables. But how do we use them.
keypair_external_idcan be left blank in this case if we are using the same public key to connect with all users. In some cases you may wish to use a unique public key for each user connection, in this case you should store the related private key somewhere with reference to the user who you are connecting to.
encrypted_recipient_nameis a record to be used by your organization only, it should identify in some way who the invitation has been created for. It should encrypted and serialized using a Cryppo serialization format (see https://github.com/Meeco/cryppo-js for more details).
public_keyhere can be unique per connection but in this case we are just going th use the keypair from the organization service.
Authorizationheader here should be the
vault_access_tokenfrom the .
organization-service-auth.yamlfrom above. To convert the
public_keyinto the format needed for betlow you can use
yq(https://mikefarah.gitbook.io/yq/) like so
cat .organization-service.yaml | yq -j eval.
invitation.jsonfile should have output that looks something like.
public_keysomewhere that we can use for this connection for Dave, dave might use the meeco keystore to manage this but in this case lets forget about the keystore for now to keep it simple.
keypair_external_idwould be a reference for Dave to retrieve the appropriate keypair (when using the keystore this would be the id of the key record) but we can just put the name of the organization service in there for this reference.
invitation_tokenhere would be
Authorizationhere should be Dave's authorization token (from
connection.jsonwill look something like.
OrganizationServicehas now made it's first connection with a user.