Help Center/ KooGallery/ Access Guide/ SaaS Access Guide V1.0 (Existing Products)/ FAQs
Updated on 2024-08-20 GMT+08:00
View PDF
Share

FAQs

  1. Why is the following error message displayed when I debug the service interface? 
    http header->bodySign is empty.

    bodySign is empty is displayed if KooGallery does not obtain the Body-Sign message header. Add Body-Sign to the response of the interface. For details, see HTTP Body Signature.

    When the service interface is invoked, the message header returned by the ISV server must contain Body-Sign, which is case sensitive. Otherwise, the message cannot be identified. For example, if the message header is Body-sign, it cannot be identified by KooGallery.

  2. Why is the error message "Failed to verify the HTTP Body signature. Expected signature value: **********" displayed when I debug the service interface?

    This is because the HTTP body content changes after the signature is obtained and before the message is sent. The possible causes of the change include attribute sequence changes, a blank space added, and a newline character added (\n is added to some output streams). Troubleshoot the issue based on the causes.

  3. When the verificateRequestParams method is invoked, authToken and signature are inconsistent, and plus signs (+) become spaces. What should I do?

    Invoke URLDecoder.decode() to decrypt authToken and signature.

  4. Why is the following error message displayed when I debug the service interface although the header contains both sign_type and signature? 
    http header->sign_type is not equals HMAC-SHA256 or signature is empty.

    The values of sign_type and signature are not obtained from the Body-Sign header. Check whether the two values returned to KooGallery are in the correct format. The correct format is as follows:

    sign_type="HMAC-SHA256", signature="MkW2WiHUOpT4G/IFYV5kigY7djPRs3U5hOCe/EQrt8g="

    If the quotation marks ("") are missing, KooGallery cannot retrieve the two values and displays this error message.

  5. Why can't a SaaS product customer view the username and password of the product when they click Manage on the My KooGallery Apps > Purchased Apps page?

    Possible causes are as follows:

    • When the instance is enabled, some parameters failed the verification. For example, the length of the password is incorrect. The length of the password ciphertext must not exceed the limit defined in this guide.
    • KooGallery failed to decrypt the username and password. Sellers must use the method provided by KooGallery to encrypt sensitive information. If a seller uses a different programming language, check whether the ciphertext generated using the current language is the same as the ciphertext generated using the code provided by KooGallery. If they are the same, check whether the encryptType parameter for encrypting and decrypting sensitive information is correctly transferred to KooGallery. If the algorithm is AES256_CBC_PKCS5Padding, the value must be 1. If the algorithm is AES128_CBC_PKCS5Padding, the value must be 2.
  6. Why is the authToken generated by encrypting the request parameters provided by KooGallery different from the authToken provided by KooGallery?

    Parameters in a requested URL are URL-encoded and cannot be directly used to generate the authToken. Decode each parameter first, and use the decoded parameters to generate the authToken. Note that a customer's mobile number and email address are ciphertexts after being decoded and do not need to be decrypted again.

  7. Does the restriction on the username and password lengths apply to the plaintexts or ciphertexts?

    It applies to the ciphertext (including the IV). Sometimes the instance of a product is successfully enabled but the username and password lengths fail the KooGallery verification. As a result, the status of the product is displayed as Enabling on the My Orders page. To prevent this issue, verify the lengths of the encrypted username and password.

  8. After a customer purchases and pays a SaaS product, KooGallery still fails to enable the instance by invoking the subscription interface of the seller when the number of invocation times reaches the maximum. What do I enable the instance?

    Find the reason why the instance fails to be enabled and take measures to rectify the issue. Then, log in to the Seller Center, choose Application Tools > Service Interface Messages in the navigation pane, and click Restart Debugging on the right.

  9. What do I do when I encounter a SaaS access problem that cannot be resolved?

    Send an email to partner@huaweicloud.com, describing the problem in detail with screenshots. The operations manager will check the email and will respond within two business days.

  10. The example code is in Java. What can I do if I use another programming language?
    • Refer to the code provided in this guide to debug your own code.
    • In addition, contact the KooGallery operations team to obtain the example code using the programming language you use to develop instances.
  11. After I debug the subscription interface on the Application Access Debugging page, do I need to do anything else that should be done?

    To ensure that subsequent service processes such as renewal, expiration, and release are normally performed, debug all of the subscription, renewal, expiration, and release interfaces before releasing a SaaS product to KooGallery.

  12. When releasing a SaaS product, where can I specify the algorithm sensitive information encryption performed during application access debugging?

    On the SaaS product release page, after you select User Authorization Required, the algorithm for encrypting sensitive information is displayed. By default, AES256_CBC_PKCS5Padding is selected. You can choose another encryption algorithm as required.

  13. What can I do if the subscription interface is successfully debugged but it cannot be invoked when a customer purchases a product?
    1. Log in to the Seller Console, choose Application Tools > Application Access Debugging in the navigation pane. Use the actual request sent by KooGallery to the customer and the actual message body returned to KooGallery to debug the subscription interface on the Application Access Debugging page.
    2. If the debugging is successful, choose Application Tools > Service Interface Messages in the navigation pane of the Seller Console and click Restart Debugging on the right of the corresponding record. Otherwise, contact the operations manager.
  14. Can multiple production system API URLs be provided for different scenarios (subscription, renewal, expiration, and release) when a product is released?

    No. Currently, only one production system API URL can be configured for a product during release.