Unpredictable login behavior after adding external gateway registration

[cumarav]

Include relevant data
z/OS 2.4 zowe v2.16

I have 2 APIMLs and want to configure them in the mode Central-Domain. So I've added AdditionalRegistration to the Domain and update Central's truststore with Domain certificate. I see 2 Gateways in the Central Eureka.
But
I've notices that login into APIML through API Catalog become unpredictable, I can click login button ~20 times with same valid credentials to get logged in, after I do couple of clicks in the catalog and it log me out.
Could you please suggest what is the limits for such a configuration Central node cannot have the GATEWAY and APICATALOG?

[pablocarle]

In a multi-tenancy configuration with API ML from Zowe v2, the accepted configuration is as follows:

• Central API ML has Spring Cloud Gateway and Discovery Service. It currently does not support having API Catalog and API Gateway.
  • The Spring Cloud Gateway act as a replacement of the Zuul-enabled Gateway and routes to both locally onboarded services and to Domain API ML instances (via URL change adding appending the apimlId)
  • Authentication is managed on the locally onboarded services and on the Domain API MLs respectively.
• Domain API ML (assuming they run on z/OS) can be normal / usual API ML installations.
  • Domain API ML needs extra metadata to register to the Central API ML, this is having an apimlId assigned and contain the information of the Central Gateway in the additionalRegistrations properties.

Of course plus establishing the trust relationship between these installations.

[balhar-jakub]

The current supported behavior is documented and as such, I am closing this issue.

[cumarav]

Based on discussion with @balhar-jakub and @pablocarle reopen it as requirement which can be eventually worked on as an enhancement