1. Is necessary? Renovation? What impact will the transformation have on ISV?

##Whether to switch can be determined according to"Introduction to Sub-Account Authorization Transformation and Upgrade" 》 Judging from the suggestions given in the document, for apps that already support sub-accounts, all will switch to the new authorization mode in mid-October; for new apps and apps that will be added later to support sub-accounts, all will use the new authorization mode. Authorization mode;

For the scope and content of influence on ISV, please refer to"Sub-account Authorization Transformation and Upgrade Impact Scope";

2. The new sub-accountsessionkey and the ## of the original parent account #sessionkeyWhat are the differences and connections?

# Similarities:

a. The acquisition method is the same, still use the authorization system provided by TOP (container authorization method or oauth authorization method), specifically Implementation parameters

Exam: //open.taobao.com/doc/category_list.htm?id=199;

b. The format of the authorization return parameters is the same: the parameters returned through the authorization request and the parsing method of the parameters have not changed;

the difference:

a. The sessionkey values ​​are different: the sessionkey returned by the old authorization mode sub-account is the same as the parent account, and the new mode sub-account and parent account sessionkey

It’s different, but there is a father-son relationship mark on the bottom of Taobao;

3. Sub-accountsessionkey Under what circumstances will it fail?

#a. After the sub-account is in arrears or is deactivated by the parent account, the current valid session key of the sub-account will become invalid, and a new one will be issued after it is reopened and used

## b. After the parent account cancels the authorization of an application to a sub-account, the currently valid session key of the sub-account will become invalid. After the parent account is reauthorized,

Reissue new sessionkey value;

c. After the ISV cancels the application’s sub-account authorization function, the session keys of all sellers’ currently valid sub-accounts will become invalid;

##4. Sub accountsessionkeywith parent accountsessionkey# Is the authorization period of ## calculated separately?

No, the authorization duration of the sub-account follows that of the parent account. Use the sub-account When the account sessionkey calls TOP's api, it will determine whether its parent account sessionkey is valid; even if the sessionkey of the

sub-account is newly issued, its authorization duration is It is consistent with the validity period of the current parent account;

##5. After the sub-account authorization modification and upgrade, what impact will it have on sellers? Will previously used apps be affected?

The impact on sellers is mainly on the operation of the authorization process. For details, please Reference"Sub-Account Authorization Transformation and Upgrade Influence Scope";

6. My application already supports sub-accounts. Do I need to cancel it now? Support sub-accounts, wait until the transformation is completed before supporting?

No, we are on the UP page (TOP Application Management → Application List) A switch button is provided. After clicking the button, it will be a new sub-account authorization mode. During the period, a compatibility will be provided for 2 months to facilitate ISV to make corresponding code changes and tests;

7. After the transformation is released, I want my application to also support subtitles Account, how should I operate it?

##For ISVs: After the transformation is released , if there are old apps that have not yet supported sub-accounts or new apps that want to support sub-accounts, check "Do you support Taobao sub-account login authorization" on the TOP Application Management → Management Permissions interface, as shown in the figure:

For sellers: Under the premise of applying "Support Taobao sub-account login authorization", the seller's main account can be There are two ways to set up in the new sub-account management system, one is to authorize application permissions by role, and the other is to authorize application permissions individually for a single sub-account. For details, see the "Sub-Account Authorization Process (New)" document;

##FAQ

about this document yet