Integrated Developer Portal not displaying Servers properly

[joshuacarino]

How to I make the developer portal output the multiple servers it has access?.

It's just that when designing the spec via Apigee and even other open api spec editors, I could select different servers as designed in the spec, see screenshot below.

But when already viewed via the developer portal. This very spec is not being rendered properly and is instead just static and only displays the very first server declared in the spec as could be seen below even though there are already multiple servers declared. It also won't show any dropdown for servers to select as it did in the spec. editor.

How do I make it be displayed properly in developer portal?.

[cjking]

I'd suggest running your spec file through a validator to confirm your syntax is good. If there are no issues then please file a support case so we can investigate why it's not being rendered.

[EdRamos]

Still encountering the same issue 2 years later

[Dayang25]

Hi, I am also encountering this issue. I would like to know if there is any update? 

[gpushpakumar]

did you find a solution for this ? This issue still exists 

[kate_p]

The issue is still there. Will it be fixed?

[anilmoregfs]

Is this issue resolved?

[Lars-Warratz]

I also came accros this issue, in scenarios were we have for example a Sandbox endpoint and a productive endpoint in the same Apigee org, i can configure the api-spec for portal to offer a login path for both target systems and can chose authentication method via a dropdown menu but from the servers configured in the spec it always just takes the first one. I don't believe it would be that difficult to offer the same kind of dropdown menu also for the server based on the array in the openapi spec that is provided.

[byz]

Hello, this is unfortunately still a known issue and gap in support - multiple servers are not supported. In the meantime, we have updated the Apigee Known Issues page with this issue for clearer communication.

[byz]

We'd also like to understand better the specific use-cases for requiring multiple servers.

Are your use-cases for multiple servers:

• differentiating between live sandbox/pre-production/production servers?
• differentiating between lifecycle versions of the same server?
• other?

Thank you in advance for your input. 

[anilmoregfs]

• It's the first use case "differentiating between live sandbox/pre-production/production servers?"
• Also, the User interface of the integrated developer portal showing the open API spec feels very outdated compared to the preview provided by any other tools such as Swargger editor, any plugins etc. Is there any way of updating it for better user experience?

[byz]

Thank you for confirming - that use-case has been well-captured on our end. 

Transparently, it's difficult to make short-term improvements in this space - user interface/experience for spec viewing and editing. We do want to address and improve the overall experience in the longer term, but have many higher priorities to work through first.