Feature blobber authorization

[Jayashsatolia403]

We need to implement an authorized blobber feature. to make it happen we need several changes in the network

• UI: user will have a way to add authorization ticket to it’s wallet in UI

• We might allow to request some service in real time to generate the ticket on request and store it in 0box
  

• User will be able to set blobber as restricted
  

• 0box: will store authorization ticket for each wallet in additional table

• Gosdk: will send ticket set in new_allocation_request and free_allocation_request for a specific blobber

•    Will send if blobber is restricted in add_blobber, update_blobber_settings
  

• Zboxcli: user will be able to use authorization ticket during allocation creation

•      User will be able to update bobbers state with is_autorizer property
  

• 0chain: for any restricted blobber appropriate authorization ticket will be verified

•     Blobber state will be extended with is_restricted
  

• Blobber: we might provide a restricted api where user can request for authorization ticket

[Jayashsatolia403]

Authorisation ticket Flow :

Blobber delegate wallet -->0box ( input : client_id, blobber_id ) : ( 0box will store authorisation ticket and client id in db ) <--> respective blobber ( input : authentication key signed by private key from 0box ) : ( output : authorisation ticket from blobber for specific client )

Client :

Client wallet <--> 0box ( input : blobber_id ) : ( output : authorisation ticket )
↓
0chain : ( input : blobbers with auth tickets ) : ( 0chain will verify from blobber pub key stored )