Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Apollo
-
Fix Version/s: Apollo
-
Component/s: None
-
Labels:None
-
Sprint:Sprint 9
Description
The current onBehalfOfUserName property in the yahooJapanCredentialsService needs to be renamed to accountID to be more in line with what YJ is expecting. The api documentation must be updated as well to reflect this.
accountID (Yahoo! Japan Sponsored Search Account ID)
onBehalfOfAccountID (Yahoo! Japan’s term, displayed in their UI and their API)
onBehalfOfPassword (password field that needs to be encrypted)
API Documentation to authenticate with their api and access their account.
https://biz.marketing.yahoo.co.jp/developercenter-en/startup/auth/
<ns1:license>xxxx-xxxx-xxxx-xxxx</ns1:license> (for API access, they provide this to us, same across all clients)
<ns1:apiAccountId>xxxx-xxxx-xxxx-xxxx</ns1:apiAccountId> (for API access, they provide this to us, same across all clients)
<ns1:apiAccountPassword>passwd</ns1:apiAccountPassword> (for API access, we control this value)
<ns1:accountId>1000000001</ns1:accountId>
<ns1:onBehalfOfAccountId>xxxxxxxxxxxxxx</ns1:onBehalfOfAccountId>
<ns1:onBehalfOfPassword>passwd2</ns1:onBehalfOfPassword>
To make this correct, onBehalfOfAccountID will be renamed to account ID and onBehalfOfUserName will be renamed to onBehalfOfAccountID.
