We are thinking of enabling mutltitenancy by creating a second organisation so 2 teams can manage their APIs and Keys without interference and overlap.
However, I’m not sure how I can ensure that a API will have a unique listen path (we would like to keep the same domain/hostname)?
Hi @markus.wiedmer,
Thank you for your patience.
Currently, there isn’t a built-in way to enforce uniqueness in this manner—each organization is expected to use a distinct domain. However, you can monitor the gateway logs for messages indicating a collision if one occurs.
"time=""May 30 05:15:57"" level=error msg=""Listen path collision, changed to /dev/bff/-1f1eb5f85a9b4c9c7074a1d8de12ce47""
You may also find this discussion helpful.