Specific Questions prior to upgrade from 5.1.2 to 5.3.2

Products

• CA API Developer Portal

Issue/Introduction

we don't understand how to enable those deprecated PAPIs and we don't see further details in the doc link you provided.
Perhaps we are wrong but:
/api-managemente/1.0/apis?portalStatus=Enabled we think is to filter the APIs published in the Portal that currently have the status=ENABLED.
It has to do with published APIs not with PAPIs.
And also, as far as we have seen, it is used in the GET to query but not for setting the status.

Environment

5.1.2

Resolution

Below is the detailed steps about the enablement of deprecated PAPI's .

Add APPLICATIONS_ENDPOINT_VERSION_5_3_1 to FEATURE_FLAG_ENABLE_DEPRECATED_API flag to enable /Applications PAPI endpoint. 
Note : FEATURE_FLAG_ENABLE_DEPRECATED_API supports comma separated values.

You can first confirm if the setting flag  FEATURE_FLAG_ENABLE_DEPRECATED_API is configured to allow access the deprecated PAPI by using the PAPI GET /tenant-admin/1.0/settings/FEATURE_FLAG_ENABLE_DEPRECATED_API endpoint like the sample below
```
curl --location 'https://apim-ssg.dev.example.com:9443/t5/tenant-admin/1.0/settings/FEATURE_FLAG_ENABLE_DEPRECATED_API' \
--header 'Content-Type: application/json;charset=UTF-8' \
--header 'Authorization: Bearer 7b69c303-92ae-46db-aa8e-d868e7f6acb8-1746579269' \
--header 'Cookie: PD-JSESSIONID=DD236BD95AFA77FC30B5C488B6522918; csrfNonce=8191a04b-d7d2-4250-b73b-9584e3bc2831; csrfNonceParam=csrf-nonce; csrfParam=authenticity-token; csrfToken=7f2b9b0822a390951f3ae40121524efdc14738529dca6c90cdeff47cd32792af34aa425c175e464834a20f9edf3aa0d2e1d44e9ac4a43af37e1a7bb88a33f074aa51c598f6a78356e9ac23e9e744f177' \
--data ''

 

If the "APPLICATIONS_ENDPOINT_VERSION_5_3_1" is not defined in the FEATURE_FLAG_ENABLE_DEPRECATED_API flag, then you can use PUT endpoint to add the APPLICATIONS_ENDPOINT_VERSION_5_3_1 to it like the sample belowcurl --location --request PUT 'https://apim-ssg.dev.example.com:9443/t5/tenant-admin/1.0/settings/FEATURE_FLAG_ENABLE_DEPRECATED_API' \
--header 'Content-Type: application/json;charset=UTF-8' \
--header 'Authorization: Bearer 7b69c303-92ae-46db-aa8e-d868e7f6acb8-1746579269' \
--header 'Cookie: PD-JSESSIONID=DD236BD95AFA77FC30B5C488B6522918; csrfNonce=8191a04b-d7d2-4250-b73b-9584e3bc2831; csrfNonceParam=csrf-nonce; csrfParam=authenticity-token; csrfToken=7f2b9b0822a390951f3ae40121524efdc14738529dca6c90cdeff47cd32792af34aa425c175e464834a20f9edf3aa0d2e1d44e9ac4a43af37e1a7bb88a33f074aa51c598f6a78356e9ac23e9e744f177' \
--data '{
  "name": "FEATURE_FLAG_ENABLE_DEPRECATED_API",
  "value": "USERS_ENDPOINT_VERSION_4_5,APIS_ENDPOINT_VERSION_4_4,APIS_ENDPOINT_2_0_VERSION_4_4,APPLICATIONS_ENDPOINT_VERSION_5_3_1,REQUESTS_ENDPOINT_VERSION_5_3_1"
}'

 

Then the /Applications should be working like the sample below