Uputstvo za upotrebu instalacijskog programa za Cisco reverzni proxy
Gotovoview
The Cisco Reverse Proxy Installer (referred to as RP Installer in this document) is a component of the Cisco Unified CCE solution. It offers a ready-made reverse proxy solution (based on Open Resty Nginx) for Unified CCE, featuring built-in, battle-tested configurations. These configurations can be used to proxy other Unified CCE components and external applications,such as ADFS, which are commonly used when deploying Unified CCE.
The RP Installer has been pre-tested and load-qualified for various usage scenarios across the deployment models supported by the Unified CCE solution.
The RP Installer facilitates access to the Unified CCE solution from the internet and is typically set up to provide VPN-less access to the Finesse Agent Desktop or enable advanced functionalities like digital channels that require direct internet ingress.
The RP Installer is intended to be deployed in a Demilitarized Zone (DMZ) on a customer-provided and hardened host running the RHEL 9.4 Operating System. The pre-configured proxying rules allow for the proxying of the following components through data-driven configuration files:
- Cisco Finesse
- Cloud Connect
- Cisco Unified Intelligence Center
- Live Data
- Cisco Identity Service
- Cisco IM&P Server
- Microsoft ADFS 3.0 or 5.0
Pažnja
The term “upstream servers” is used in this guide to refer to all the solution components such as Finesse, CUIC, IdS, and IM&P servers that are configured to be accessed through reverse-proxy
Preduvjeti
To configure VPN-less access to the Finesse desktop:
- Reverse Proxy Installer must be 15.0(1) or above
- Finesse, IdS, and Cisco Unified Intelligence Center must be 12.6(2) ES4 or above.
- In coresident deployments, LiveData and Cisco Unified Intelligence Center should be 12.6(2) or above
- Unified CCE and LiveData standalone must be 12.6 (1) or above with the latest ES for the respective versions
- Cisco IM&P Server
- DMZ with internet connectivity must be available to host the reverse-proxy.
Sigurnost
RP instaler nije otvoreni proxy; on autentificira sve zahtjeve prije nego što ih proslijedi odgovarajućem uzvodnom serveru. Uzvodni serveri također primjenjuju lokalnu autentifikaciju prije obrade zahtjeva.
Beyond authentication, there are several additional sigurnost measures available to protect the solution. Details about security can be found in the Security chapter.
For information about security guidelines, see the Security Guidelines for Reverse-Proxy Deployment in
Security Guide for Cisco Unified ICM/Contact Center Enterprise.
Za više informacija o autentifikaciji, pogledajte Autentifikacija.
Mapiranje hosta File za mrežno prevođenje
Implementacija obrnutog proxyja oslanja se na mapiranje file koje je administrator obezbijedio za konfigurisanje liste eksterno vidljivih kombinacija imena hosta/porta i njihovog mapiranja na stvarna imena servera i portove koje koriste Finesse, IdS i CUIC serveri. Ovo mapiranje file koja je konfigurirana na uzvodnim serverima je ključna konfiguracija koja omogućava klijentima povezanim putem interneta da budu preusmjereni na potrebne hostove i portove koji se koriste na internetu. Za više informacija o mapiranju, pogledajte Popunjavanje podataka za mrežno prevođenje.
Napomena
It is recommended to use a dedicated web server unutar LAN-a za hostovanje mapiranja file, umjesto korištenja instalacijskog programa za reverzni proxy u tu svrhu.
Za sve zahtjeve koji dolaze putem obrnutog proxyja, Finesse, IdS i CUIC serveri provjeravaju mapiranje hosta. file, to translate the internal host names and ports that are used on the LAN. They are translated to the publicly resolvable host names and ports that have to be used on the internet. This mapping file, koja se naziva mapa konfiguracije proxyja file, is the key configuration that allows the clients connected over the reverse proxy to be redirected to the required hosts and ports that are used on the internet.
Mapa konfiguracije proxyja file može se konfigurirati korištenjem CLI-ja dostupnog na Finesse, IdS i CUIC serverima. Za detalje o mapiranju file format i konfigurirane podatke, pogledajte odjeljak Popunjavanje podataka za mrežno prevođenje. Za detalje o CLI-ju koji se koristi za konfiguriranje file, refer to the utils system reverse-proxy config-uri CLI in the topic Configure Proxy Mapping by Using CLI.
Mapa konfiguracije proxyja file može se konfigurirati korištenjem CLI-ja dostupnog na Unified CCX serverima i Cisco Collaboration Platform serverima. Za detalje o mapiranju file format i konfigurirane podatke, pogledajte odjeljak Popunjavanje podataka za mrežno prevođenje u Vodiču za administraciju i operacije za Cisco Unified Contact Center Express. Za detalje o CLI-ju koji se koristi za konfiguriranje file, refer to the Configure Proxy Mapping by Using CLI section in Cisco Unified Contact Center Express Administration and Operations Guide available
at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-express/products-maintenance-guides-list.html..
Port Management
Jedan od glavnih aspekata dizajna pri implementaciji obrnutog proxyja su domena i portovi koji se koriste za pristup aplikaciji. Ovi aspekti su međuzavisni i utiču jedan na drugi prilikom dizajniranja implementacije.
Obrnuti proxy mora biti u stanju odrediti kojem uzvodnom serveru se može proslijediti dolazni zahtjev, a kamo treba proslijediti dolazni zahtjev. To se može postići promjenom porta ili imena hosta koji se koristi za pristup aplikaciji. U suštini, kombinacija hosta i porta mora biti jedinstvena kako bi proxy mogao razlikovati i usmjeriti promet na ispravnu uzvodnu komponentu, a to je uvjet da se proxy uopće ispravno pokrene.
Stoga su ovo dostupne opcije za dizajniranje pristupa domenu i portu:
- Use a common domain and differentiate application access using multiple ports.
- Use a common port and differentiate application access using multiple domains
Nakon što se odredi domen i distribucija portova, potrebno je poduzeti sljedeće korake:
- Proxy map configuration has to be changed to match the port and domain required. See Configure Proxy Mapping by Using CLI.
- The respective upstream component environment configuration in the reverse proxy installer has to be configured with the required hostname and port, see Configure deployment environment configurations
Korištenje zajedničke domene s više portova
Sljedeći prample ilustruje kako se više aplikacijskih servera može konfigurirati korištenjem ovog obrasca pristupa:
- FinesseA = ReverseProxyDomain.com:8445
- FinesseB = ReverseProxyDomain.com:8446
- Finesse1A = ReverseProxyDomain.com:8447
- Finesse2B = ReverseProxyDomain.com:8448
The following are the benefits of using multiple ports:
- More granular packet level rate-limits applicable to each application can be applied at the ingress point to control rate-limits. Domain-level access means that the rate-limits can’t be granular.
- A single-domain requires only a single SSL certificate to access the application. It could be a factor in reducing costs, unlike a multiple-domain application which requires a wildcard certificate.
Sljedeći su nedostacitages in using multiple ports:
- Certain network deployments like CDNs don’t support custom ports.
- Security devices that automatically apply security rules might require custom configurations with non-standard ports.
- Multiple ports must be opened in the DMZ firewall (10–15 ports are required for a standard 2k deployment). This isn’t recommended by the network security teams.
- There’s an increased overhead regarding the port manageability.
- Deploying new instances of the application requires firewall/network changes.
Napomena
Ports other than the ones mentioned in the Proxy Map must be blocked and shouldn’t be available for access on the reverse proxy host. This must be blocked at the ingress point as the proxy doesn’t currently have rules to block this access at network level.
The Cisco provided installer supports running multiple instances which cater to different sets of upstream servers, to aid in ease of maintenance. Multiple instances of the installer don’t allow to use the same ports across different instances of the proxy. Only one process can bind to the same TCP port.
Consider the above two points when deciding the port management strategy against proxy installer configuration.
Korištenje zajedničkog porta i više domena
Sljedeći prample illustrates how multiple application servers can be configured using this access pattern.:
- FinesseA = FinesseA-ReverseProxyDomain.com:443
- FinesseB = FinesseB-ReverseProxyDomain.com:443
- Finesse1A = Finesse1A-ReverseProxyDomain.com:443
- Finesse2B = Finesse2B-ReverseProxyDomain.com:443
Konfiguracija s jednim portom obrće gore navedene prednosti i nedostatke kod konfiguracije s više portova.
Napomena
Supporting a single port of access requires Unified Intelligence Center and LiveData components to be on 12.6(2)versions.
DNS konfiguracija za Finesse, IdS i CUIC servere
Svaki Finesse, IdS, CUIC, IM&P i komponentni server treće strane koji odgovara hostu kojem je potreban pristup internetu mora biti adresabilan s interneta. To zahtijeva da se naziv hosta i pridruženi port, koji se može razlučiti s interneta, mapiraju na javni port i odgovarajuću IP adresu obrnutog proxyja tako da se promet usmjerava na odgovarajuće komponentne servere.
DNS registration of the publicly resolvable host names and the corresponding IP addresses is mandatory before the requests reach the reverse-proxy.
SSL certifikati
For the hostnames that are configured, corresponding to each unique hostname that is used by the internet client, the respective certificates must be acquired and configured on the reverse-proxy. Even though self signed certificates are supported, they are risky because the users access directly from the internet. The clients can be more secure by using CA-signed certificates. The best practice is to get CA certificates for proxy servers and third-party-gadget servers.
Dokumenti / Resursi
 |
Instalater obrnutog proxyja od strane Cisco-a [pdf] Uputstvo za upotrebu Instalater obrnutog proxyja, Instalater proxyja, Instalater |