fixup! documentation

Signed-off-by: Angelo De Caro <[email protected]>

Author: adecaro

docs/services/identity.md

@@ -76,3 +76,16 @@ Both implementations leverage the concept of Hyperledger Fabric MSP ([https://hy
 
 * **MSP X.509:** This implementation retrieves long-term identities from local folders adhering to the X.509-based MSP format.
 * **MSP Idemix:** This implementation loads long-term identities from local folders that follow the Idemix-based MSP format.
+
+## Using the Identity Service in a Token Driver
+
+If you want to use the Identity Service in your Token Driver, then here is what you need to do.
+
+First, instantiate your roles. The identity service come equipped with two `Role` implementation.
+One is based on X.509 certificates, the other one is based on Idemix. 
+Both requires the identities to be stored following the Hyperledger Fabric MSP prescriptions. 
+
+High level, these are the steps to follow:
+1. Instantiate the roles your driver will support.
+2. Instantiate the Identity Provider passing the constructed roles.
+3. Instantiate the Wallet Registries for each role.

token/driver/identity.go

@@ -44,6 +44,8 @@ type IdentityProvider interface {
 	// RegisterAuditInfo binds the audit information to the passed identity
 	RegisterAuditInfo(id view.Identity, auditInfo []byte) error
 
+	WalletIDs(role IdentityRole) ([]string, error)
+
 	// GetAuditInfo returns the audit information associated to the passed identity, nil otherwise
 	GetAuditInfo(identity view.Identity) ([]byte, error)