Support Extra Specs to Subscription-confirming
Registered by
wanghao
This requirement came from a true scenario,when people use the subscription function of Zaqar, for example, text messages, they need to return some extra information like message authentication code in confirming process. Now Zaqar still can’t support it, that will impact the usage of subscription.
Blueprint information
Related branches
Related bugs
Sprints
Whiteboard
(?)