Unable to remove Proxy after failed Gateway deployment

Products

• CA API Developer Portal

Issue/Introduction

When attempting to remove a Proxy following a failed deployment in the API Developer Portal , the operation fails with the following error:

Error: KeyStoreUuid : [UUID] The Key Store With Proxies assigned cannot be deleted.

This occurs even after attempting standard cleanup procedures outlined in the installation documentation for failed gateway deployments.

Environment

All Supported versions of API Portal/ Gateway.

Cause

 This error is triggered when API keys retain active OAUTH_TYPE associations in the database. The system prevents the deletion of a keystore if it is still linked to API proxies, and these database associations prevent the deletion of those proxies.

Resolution

To resolve this issue, you must manually update the OAUTH_TYPE field in the portal database.

Warning: Before running any database update commands, ensure you have a full, verified backup of your API Developer Portal database.

1. Access your portal database.

2. Execute the following SQL command to set the OAUTH_TYPE to null for keys that are not public or confidential:

   sql

    

   UPDATE APPLICATION_API_KEY SET OAUTH_TYPE=null WHERE OAUTH_TYPE IS NOT NULL AND OAUTH_TYPE NOT IN ('PUBLIC','CONFIDENTIAL');

3. Once the update is successful, return to the API Developer Portal UI.

4. Navigate to the API Proxy page.

5. Retry the deletion of the API proxy. It should now proceed without the previous "Key Store With Proxies assigned" error.

6. Proceed with the remaining steps of your keystore cleanup process as documented.