You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Readme.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,11 @@ The proxy is non-intrusive and independent of any specific version of Spark Hist
22
22
23
23
## Installation
24
24
25
-
To deploy the spark web proxy, refer to helm chart [README](helm/spark-web-proxy/README.md) for customization options and installation guidelines.
25
+
To deploy the Spark Web Proxy, refer to helm chart [README](helm/spark-web-proxy/README.md) for customization options and installation guidelines.
26
26
27
27
The web proxy can also be deployed as a sidecar container alongside your existing Spark History Server. Ensure to set the property `configuration.spark.service` to `localhost`.
28
28
29
-
In both cases, you need to use the spark web proxy ingress instead of your spark history ingress.
29
+
In both cases, you need to use the Spark Web Proxy ingress instead of your spark history ingress.
[Spark Authentication Filter](https://github.com/OKDP/okdp-spark-auth-filter) can be applied to both Spark History Server and Spark Jobs to enable user authentication and authorization.
104
+
The Spark Web Proxy is independent of any specific authentication mechanism. It simply forwards credentials and headers to the running Spark instances without modifying or enforcing authentication itself.
105
+
106
+
This allows to use the [Spark Authentication Filter](https://github.com/OKDP/okdp-spark-auth-filter) or any other authentication solution to secure both the Spark History Server and Spark Jobs to ensure user authentication and authorization.
0 commit comments