Less confusing handling of keyring network names in CLI

[vipyne]

Allow a keyring URL ie http://keyrings.ara.one/1.0/did:ara:59f8d0... to be passed in without a network name specified in the URL. Use the network name passed in via --network arg.

Desired Behavior

$ aid resolve did:ara:4d9a84... \
-k http://keyrings.ara.one/1.0/did:ara:59f8d...71a87987ef -n archiver -s test-node

Actual Behavior

$ aid resolve did:ara:4d9a84... \
-k http://keyrings.ara.one/1.0/did:ara:59f8d...71a87987ef/archiver -n resolver -s test-node

[Prash74]

@vipyne so the --network flag in ara-identity CLI refers to the network name inside the keyring file.

So the keyring file stores network keys in a key-value pair format. Something like this

$ ank -i did:ara:59f8d.....7ef -s test-node -n archiver -k keyring-file

will result in,

{
"archiver" : {Network keys containing the discovery key }
}

Lets say if we append another entry into the same keyring file as below,

$ ank -i did:ara:59f8d.....7ef -s test-node -n resolver -k keyring-file

It will result in the keyring file looking something like this,

{
"archiver" : {Network keys containing a discovery key},
"resolver" : {Network keys containing a discovery key}
}

So, lets say you want to retrieve the discovery key for the archiver entry from the above file, you would use it as

$ aid archive <DID> -s test-node -n archiver -k keyring-file.pub

As for the keyring-registry URL's, the name in the URL refers to the file name used to store when publishing. The registry server treats it as a single file and doesn't care about what values are inside the keyring file.

In order to use a keyring file from the registry, you would need to know the shared-secret and network values inside the keyring file beforehand. This can be obtained from the developer who provided the URL for the keyring file.

So if the same file above is published as ara-dev-keyring and the URL is http://keyrings.ara.one/1.0/did:ara:59f8d...71a87987ef/ara-dev-keyring, it can used as

$ aid archive <DID> -s test-node -n archiver -k 'http://keyrings.ara.one/1.0/did:ara:59f8d...71a87987ef/ara-dev-keyring'

$ aid resolve <DID> -s test-node -n resolver -k 'http://keyrings.ara.one/1.0/did:ara:59f8d...71a87987ef/ara-dev-keyring'

[vipyne]

ah, I think this explains the difference between name and network.
Thanks @Prash74 !