Cisco alderantzizko proxy instalatzailearen erabiltzailearen eskuliburua
Amaituview
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
- Hodei Konektatu
- Cisco Unified Intelligence Center
- Zuzeneko datuak
- Cisco Identity Service
- Cisco IM&P Server
- Microsoft ADFS 3.0 or 5.0
Arreta
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
Aurrebaldintzak
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.
Segurtasuna
RP instalatzailea ez da proxy irekia; eskaera guztiak autentifikatzen ditu goiko zerbitzari egokira bidali aurretik. Goiko zerbitzariek tokiko autentifikazioa ere betearazten dute eskaerak prozesatu aurretik.
Beyond authentication, there are several additional segurtasuna 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.
Autentifikazioari buruzko informazio gehiago lortzeko, jo Autentifikazioa atalera.
Ostalariaren mapaketa File Sareko itzulpenerako
Alderantzizko proxyaren hedapena mapaketa batean oinarritzen da file administratzaileak emandakoa kanpoan ikusgai dauden hostname/ataka konbinazioen zerrenda eta Finesse, IdS eta CUIC zerbitzariek erabiltzen dituzten benetako zerbitzari izen eta atakekin duten mapaketa konfiguratzeko. Mapaketa hau file Goiko zerbitzarietan konfiguratuta dagoena da Interneten konektatutako bezeroak Interneten erabiltzen diren beharrezko ostalari eta portuetara birbideratzeko aukera ematen duen konfigurazio nagusia. Mapei buruzko informazio gehiago lortzeko, jo Sareko itzulpen datuak bete atalera.
Oharra
dedikatu bat erabiltzea gomendatzen da web LANeko zerbitzaria mapaketa ostatatzeko file, helburu horretarako Alderantzizko Proxy instalatzailea erabili beharrean.
Alderantzizko proxyaren bidez datozen eskaera guztietarako, Finesse, IdS eta CUIC zerbitzariek host mapaketa egiaztatzen dute. 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, Proxy-konfigurazio mapa bezala ezagutzen dena 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.
Proxy konfigurazio mapa file Finesse, IdS eta CUIC zerbitzarietan eskuragarri dagoen CLI erabiliz konfigura daiteke. Mapei buruzko xehetasunak lortzeko file formatua eta konfiguratutako datuak kontuan hartuta, jo ezazu Sareko itzulpen datuak bete atalera. Konfiguratzeko erabilitako CLIari buruzko xehetasunak lortzeko file, refer to the utils system reverse-proxy config-uri CLI in the topic Configure Proxy Mapping by Using CLI.
Proxy konfigurazio mapa file Unified CCX zerbitzarietan eta Cisco Collaboration Platform zerbitzarietan eskuragarri dagoen CLI erabiliz konfigura daiteke. Mapei buruzko xehetasunak lortzeko file formatua eta konfiguratutako datuak kontuan hartuta, jo Cisco Unified Contact Center Express administrazio eta eragiketa gidan Sarearen itzulpen datuak bete atalera. Konfiguratzeko erabilitako CLIari buruzko xehetasunak lortzeko. 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..
Portuko Kudeaketa
Alderantzizko proxy bat ezartzerakoan diseinu-alderdi nagusietako bat domeinua eta aplikazioa atzitzeko erabiltzen diren portuak dira. Alderdi hauek elkarren mendekoak dira eta elkarri eragiten diote hedapena diseinatzerakoan.
Alderantzizko proxyak zehaztu ahal izan behar du zein zerbitzari goranzkoetara birbidal daitekeen sarrerako eskaera bat, eta nora birbidal daitekeen. Horretarako, aplikaziora sartzeko erabiltzen den ataka edo host-izena aldatu behar da. Funtsean, host-aren eta atakaren konbinazioa bakarra izan behar da proxyak trafikoa bereizi eta goiko osagai zuzenera bideratzeko, eta proxyak behar bezala abiarazteko ere baldintza bat da.
Beraz, hauek dira domeinua eta portua sartzeko aukera diseinatzeko dauden aukerak:
- Use a common domain and differentiate application access using multiple ports.
- Use a common port and differentiate application access using multiple domains
Domeinua eta portuen banaketa zehaztu ondoren, urrats hauek eman behar dira:
- 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
Portu anitz dituen domeinu komun bat erabiltzea
Hurrengo example-k sarbide-eredu hau erabiliz hainbat aplikazio-zerbitzari nola konfigura daitezkeen erakusten du:
- 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.
Honako hauek dira desabantailaktages 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.
Oharra
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.
Portu komun bat erabiliz eta domeinu anitzekin
Hurrengo example 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
Ataka bakarreko konfigurazioak goian zerrendatutako alde onak eta txarrak alderantzikatzen ditu ataka anitzeko konfigurazioarekin.
Oharra
Supporting a single port of access requires Unified Intelligence Center and LiveData components to be on 12.6(2)versions.
DNS konfigurazioa Finesse, IdS eta CUIC zerbitzarietarako
Interneterako sarbidea behar duen host bati dagokion Finesse, IdS, CUIC, IM&P eta hirugarrenen osagai-zerbitzari bakoitza Internetetik helbideragarria izan behar da. Horrek eskatzen du Internetetik ebaz daitekeen host-izen bat eta lotutako portu bat alderantzizko proxyaren portu publikora eta IP helbidera mapatzea, trafikoa dagokion osagai-zerbitzarietara bideratzeko.
DNS registration of the publicly resolvable host names and the corresponding IP addresses is mandatory before the requests reach the reverse-proxy.
SSL ziurtagiriak
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.
Dokumentuak / Baliabideak
 |
Cisco alderantzizko proxy instalatzailea [pdf] Erabiltzailearen eskuliburua Alderantzizko Proxy Instalatzailea, Proxy Instalatzailea, Instalatzailea |