From 0f86176678986005ae1a0cfa3f2785d70673e256 Mon Sep 17 00:00:00 2001
From: Simon John <sjohn@tuxcare.com>
Date: Wed, 19 Mar 2025 14:14:16 +0000
Subject: [PATCH] Updated Radar docs with instructions regarding proxying via
 ePortal 2.16+

Added note about restart eportal
---
 docs/radar/README.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/docs/radar/README.md b/docs/radar/README.md
index 77c022801..762b72717 100644
--- a/docs/radar/README.md
+++ b/docs/radar/README.md
@@ -99,6 +99,37 @@ For running manually, you may need to set it in the user profile like so (or sim
 echo "export https_proxy=http://proxy.domain.com:port" > /etc/profile.d/proxy.sh
 ```
 
+## Proxying via ePortal
+
+If you are an [ePortal](/eportal) user, you can proxy Radar via ePortal instead of configuring a dedicated proxy as above.
+
+In /etc/tuxcare-radar/radar.yaml change the `base-url` to point to your eportal server with a trailing `/radar`, for example:
+
+```text
+#base-url: https://radar.tuxcare.com
+base-url: https://eportal.example.com/radar
+```
+
+Then on your ePortal server, update /etc/eportal/config with the following:
+
+```text
+RADAR_PROXY_ENABLE = True
+```
+
+Then restart ePortal:
+
+```text
+systemctl restart eportal
+```
+
+When it is working, you will see messages like the following, mentioning the ePortal URL in /var/log/tuxcare-radar/radar.log on your TuxCare Radar client:
+
+```text
+radar INFO: fetching oval file from https://eportal.example.com/radar/oval/alma/9.5?fips=false&oval=0
+radar INFO: fetching oval file from https://eportal.example.com/radar/oval/alma/9.5?fips=false&oval=1
+radar INFO: sending output to https://eportal.example.com/radar
+```
+
 ## Usage
 
 The installer should have created an /etc/cron.d/tuxcare-radar file that will run from a randomized time every 6 hours, it will check if a scan has been run in the last 23 hours (`time-between-runs` in radar.yaml) and if not, it will run a scan.