Description

Summary

When mandatory additional API properties are configured via the Admin Portal tenant configuration (tenant-config.json), the Publisher portal fails to load the Lifecycle page for MCP Servers. The page remains in a loading state and the browser console shows a JS error from LifeCycleUpdate.jsx indicating .find() is called on an undefined value. The same configuration works as expected for REST APIs. In debugging, the api object for MCP servers is missing api.additionalProperties (undefined), while REST APIs include it (array).

Steps to Reproduce

Reproducing steps

1. Add the following to the Admin Portal advanced tenant configuration (tenant-config.json) to define mandatory properties:

   "PropertyConfigurations": {
     "Properties": [
       {
         "Name": "PROPERTY-ONE",
         "Required": true,
         "Description": "Description of PROPERTY-ONE"
       },
       {
         "Name": "PROPERTY-TWO",
         "Required": true,
         "Description": "Description of PROPERTY-TWO"
       }
     ]
   }

2. Restart / apply the configuration so it reflects in Publisher.
3. In Publisher, create a REST API and verify the custom properties appear under API Properties (works as expected).
4. In Publisher, create an MCP Server and navigate to its Lifecycle page.
5. Observe the page keeps loading and console shows:

LifeCycleUpdate.jsx:258 Error fetching settings: TypeError: Cannot read properties of undefined (reading 'find')
    at LifeCycleUpdate.jsx:244:79
    at Array.every (<anonymous>)
    at LifeCycleUpdate.jsx:243:88

6. In browser debugging mode, compare api object:

• REST API: api.additionalProperties is present (array)
• MCP Server: api.additionalProperties is missing/undefined

Version

4.6.0

Environment Details (with versions)

No response