IBM Support

LI81811: 500 ERROR PUBLISHING TO A SPACE AN API WITH API PROTECTION SOURCE SET TO HEADER OR/AND TLS-CERT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When you try to publish, in catalog space, an API with
    Application Authentication turned on and API Protection source
    set to  header (or tls-cert), it fails with a 500 error.
    Reproduction steps:
    -------------------
    1- Create an API with a application-authentication turned on
    and API Protection source set to header (or tls-cert)
    ====
    application-authentication:
      certificate: true
    application-authentication-source:
      - header (or tls-cert)
    ===
    2- Publish the API to a catalog where space was enabled and
    configured with a datapower api gateway service.
    Result:
    The publishing the catalog space fails with 500 error.
    ====
    Product has not been published!
    An internal error occurred.
    View error ID
    500 API Error
    October 29, 2020 10:28 AM
    =====
    Searching for the log with the error ID you see:
    ---
    2020-10-29T09:17:11.255Z audit
    [fb431aaedcf0dd877aa23dd61663a59d] START: >>>>>>>> [POST]:
    /api/spaces/1824456a-f483-4782-85b7-508694bdae06/test-space/923f
    6b9f-e261-4e40-8531-ab7225f2b2da/publish-draft-product
    2020-10-29T09:17:11.369Z apim:routes:product
    [fb431aaedcf0dd877aa23dd61663a59d] CREATE API (No existing
    API): testapicert-apigw:1.0.0
    2020-10-29T09:17:11.560Z bhendi:error
    [fb431aaedcf0dd877aa23dd61663a59d] Original error message:
    Cannot read property 'results' of undefined
    2020-10-29T09:17:11.561Z bhendi:error
    [fb431aaedcf0dd877aa23dd61663a59d] Error in POST
    post:/api/spaces/:org/:catalog/:space/apis (api.js:create)
    2020-10-29T09:17:11.561Z bhendi:error
    [fb431aaedcf0dd877aa23dd61663a59d] invoker::invoke, error for
    call to post
    /spaces/1824456a-f483-4782-85b7-508694bdae06/08d3329d-b761-4f16-
    aac5-32eb427413ec/923f6b9f-e261-4e40-8531-ab7225f2b2da/apis
    (operation id: api_createSpaceScope):
    {"status":500,"message":["An internal error occurred."]}
    2020-10-29T09:17:11.561Z bhendi:error
    [fb431aaedcf0dd877aa23dd61663a59d] Error in POST
    post:/api/spaces/:org/:catalog/:space/products
    (product.js:create)
    2020-10-29T09:17:11.562Z bhendi:error
    [fb431aaedcf0dd877aa23dd61663a59d] invoker::invoke, error for
    call to post
    /spaces/1824456a-f483-4782-85b7-508694bdae06/08d3329d-b761-4f16-
    aac5-32eb427413ec/923f6b9f-e261-4e40-8531-ab7225f2b2da/products?
    gateway_services=api-gw-service (operation id:
    product_createSpaceScope): {"status":500,"message":["An
    internal error occurred."]}
    2020-10-29T09:17:11.563Z bhendi:error
    [fb431aaedcf0dd877aa23dd61663a59d] Error in POST
    post:/api/spaces/:org/:catalog/:space/publish-draft-product
    (space.js:publishDraftProduct)
    2020-10-29T09:17:11.564Z audit
    [fb431aaedcf0dd877aa23dd61663a59d] Stack trace for response
    error: Error: An internal error occurred.
    2020-10-29T09:17:11.564Z audit
    [fb431aaedcf0dd877aa23dd61663a59d] END:  <<<<<<<< FAILURE:
    [500] response (POST
    /api/spaces/1824456a-f483-4782-85b7-508694bdae06/test-space/923f
    6b9f-e261-4e40-8531-ab7225f2b2da/publish-draft-product) (took
    309ms)
    [fb431aaedcf0dd877aa23dd61663a59d] {
    2020-10-29T09:17:11.564Z apicutil:profile:metrics
    [fb431aaedcf0dd877aa23dd61663a59d]
    ;POST;/api/spaces/1824456a-f483-4782-85b7-508694bdae06/test-spac
    e/923f6b9f-e261-4e40-8531-ab7225f2b2da/publish-draft-product;309
    .12464106082916;126.11074900627136;32;1;50;0
    2020-10-29T09:17:11.564Z bhendi:server
    [fb431aaedcf0dd877aa23dd61663a59d]  - Serializing as
    application/json
    ----
    

Local fix

  • Publish the API without API Protection source and manually set
    the API Definition at in the DataPower gateway UI
    

Problem summary

  • The API which has application authentication enabled in it
    cannot publish to space successfully.
    

Problem conclusion

  • in 10.0.1.1, backend code has been modified to also look for
    space when it detecting the gateway service.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI81811

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-29

  • Closed date

    2021-01-31

  • Last modified date

    2021-01-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

  • RA0X PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2021