CustomParameters values not setting

[Vsetecka7]

Location : https://apim.docs.wso2.com/en/3.2.0/learn/api-controller/advanced-topics/configuring-different-endpoint-security-types/

I have a issue with customParameter attribute (scope: test). However i set any key-value pairs, I still don't see them in the endpoint.

Here is part of my api.yaml downloaded from apim after setting parameter manually in GUI:

  endpointConfig:
    endpoint_type: http
    endpoint_security:
      production:
        tokenUrl: https://apim.cz/apitest/rest/v1/auth/oauth2/token
        clientId: testId
        clientSecret: testSecret
        customParameters:
          scope: test
        additionalProperties: {}
        type: OAUTH
        grantType: CLIENT_CREDENTIALS
        enabled: true

When I try to use the exact same yaml for update (via apictl 4.0), It doesn't set the value, and the downloaded api.yaml looks like this: customParameters: {}

[msm1992]

Hi @Vsetecka7,

• The recommended APICTL version to be used with APIM 3.2.0 is 3.2.x not 4.0. You can download the latest 3.2.x apictl version from [1].
• I tested below scenario with APIM 3.2.0(both latest U2 and U2 level 0) and APICTL 3.2.9 and the custom parameters were imported as expected.
  • Created an API, configured endpoint security with OAUTH client_credentials and added a custom parameter. Downloaded the API and checked the customParameters under endpoint_security and this was properly set.
  • Next I tried to create and update aa API by importing the above downloaded API artifact via apictl 3.2.9. In this case also custom property was properly set(verified via GUI).
• Can you please try using the APICTL 3.2.x version and see if this works ? Also please let me know if the steps I mentioned above are different from what you were trying.

[1]. https://apim.docs.wso2.com/en/3.2.0/learn/api-controller/getting-started-with-wso2-api-controller/#download-and-initialize-the-ctl-tool

Thanks,
Sachini

[msm1992]

Hi Team,

I also tested above scenario with APIM 4.4.0 rc2 and APICTL 4.4.0-beta distributions and no issues were identified.

Thanks,
Sachini

[msm1992]

Closing the ticket since the mentioned bug cannot be recreated.

[Vsetecka7]

Thanks, it solved my problem. In version 4.2. seems like it's working properly.