SRS - How to secure with https ?
Hi,
I see that SRS Search and Reporting is using port 8080.
SRS is using micronaut.
Is there a way for Pega to call to SRS with secure https ?
Accepted Solution
Updated: 5 May 2025 21:17 EDT
HCA Healthcare
US
@MingEeL4 Since you cannot modify the application.yml file inside the SRS JAR provided by Pega, the best approach is to set up HTTPS using environment variables or a reverse proxy. One common solution is to place a reverse proxy like NGINX or Apache in front of SRS. You can configure the proxy to handle HTTPS (by installing an SSL certificate) and forward secure traffic to the internal SRS service running on port 8080. This way, SRS itself still runs on HTTP, but all external communication happens over HTTPS. Then, in Pega, configure the search node URL to use https:// pointing to the reverse proxy. This setup avoids modifying the JAR and ensures secure communication between Pega and SRS.
HCA Healthcare
US
@MingEeL4 Yes, you can secure the SRS (Search and Reporting Service) with HTTPS instead of using the default HTTP port 8080. Since SRS is built on Micronaut, it supports HTTPS configuration. To enable HTTPS, you need to generate or obtain a valid SSL/TLS certificate (either self-signed or from a certificate authority) and configure it in the application.yml or application.properties file of SRS. Update the configuration to include the keystore path, password, and type under the micronaut.server.ssl section. Once configured, restart the SRS service, and it will start listening on a secure port like 8443. In Pega, update the Search Node settings in Admin Studio to use https:// with the correct port. This ensures all communication between Pega and SRS is encrypted and secure.
Updated: 5 May 2025 1:28 EDT
SWIFT
MY
Thanks @Sairohith,
I should not update the application.yml as it is in the SRS JAR that comes from the Pega's provided image.
In the application.yml, micronaut.server.ssl section not available.
micronaut:
http:
client:
read-timeout: 30s
server:
host: ${APPLICATION_HOST:localhost}
port: ${APPLICATION_PORT:8080}
cors:
enabled: true
Accepted Solution
Updated: 5 May 2025 21:17 EDT
HCA Healthcare
US
@MingEeL4 Since you cannot modify the application.yml file inside the SRS JAR provided by Pega, the best approach is to set up HTTPS using environment variables or a reverse proxy. One common solution is to place a reverse proxy like NGINX or Apache in front of SRS. You can configure the proxy to handle HTTPS (by installing an SSL certificate) and forward secure traffic to the internal SRS service running on port 8080. This way, SRS itself still runs on HTTP, but all external communication happens over HTTPS. Then, in Pega, configure the search node URL to use https:// pointing to the reverse proxy. This setup avoids modifying the JAR and ensures secure communication between Pega and SRS.