Good morning
We currently have an API Connect v5c 10.0.5.1 setup,
on production which hosts three catalogues:
"- fatturazione"
"- integrazioni"
"- interventi"
These APIs and related products that are hosted on these catalogs are all reachable from the same FQDN https://apic.digibyte.it.
This is limiting our flexibility,
when assigning certain restrictions/policies at the catalog level,
so we wanted to see what options we have.
What we want to achieve is to have three distinct FQDNs:
https://fatturazioneapic.digibyte.it
https://integrazioniapic.digibyte.it
https://interventiapic.digibyte.it
so that traffic on these endpoints is delivered to the correct catalog.
While researching online, we discovered that the concept of Vanity Endpoints exists: https://medium.com/@nisha.narayanan/vanity-endpoints-legacy-behavior-e6f69e09a97f.
Is it something that can help us achieve what we want?
And if so, are there other configurations to do to fully achieve what we want?
I took a look at the configurations in our catalog and the Vanity Endpoints are all configured on https://apic.digibyte.it.
We would appreciate any advice on this.
Thanks in advance
Emil C.
------------------------------
Emiliano Canova
------------------------------