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
The STAC Auth Proxy can be deployed to Kubernetes via the [Helm Chart available on the GitHub Container Registry (GHCR)](https://github.com/developmentseed/stac-auth-proxy/pkgs/container/stac-auth-proxy%2Fcharts%2Fstac-auth-proxy).
|`env`| Environment variables passed to the container | No |`{}`|
28
+
|`ingress.enabled`| Enable ingress | No |`true`|
29
+
|`ingress.className`| Ingress class name | No |`nginx`|
30
+
|`ingress.host`| Hostname for the ingress | No |`""`|
31
+
|`ingress.tls.enabled`| Enable TLS for ingress | No |`true`|
32
+
|`replicaCount`| Number of replicas | No |`1`|
33
+
34
+
For a complete list of values, see the [values.yaml](https://github.com/developmentseed/stac-auth-proxy/blob/main/helm/values.yaml) file.
35
+
36
+
## Authorization
2
37
3
38
The chart provides two levels of authorization:
4
39
5
-
1.**[Route-level authorization](https://developmentseed.org/stac-auth-proxy/user-guide/route-level-auth/)**: Controls which API endpoints are accessible and by whom
6
-
2.**[Record-level authorization](https://developmentseed.org/stac-auth-proxy/user-guide/record-level-auth/)**: Filters collections and items based on user permissions
40
+
1.**[Route-level authorization](route-level-auth.md)**: Controls which API endpoints are accessible and by whom
41
+
2.**[Record-level authorization](record-level-auth.md)**: Filters collections and items based on user permissions
7
42
8
-
## Route-Level Authorization
43
+
###Route-Level Authorization
9
44
10
45
Configure via `authorization.route` section in `values.yaml`.
11
46
12
-
### Mode: `default` (Recommended)
47
+
####Mode: `default` (Recommended)
13
48
14
49
Public catalog with protected write operations. This is the most common configuration.
15
50
@@ -21,7 +56,7 @@ authorization:
21
56
22
57
This automatically sets `DEFAULT_PUBLIC=true`, making all read endpoints public while requiring authentication for write operations.
23
58
24
-
### Mode: `custom`
59
+
#### Mode: `custom`
25
60
26
61
Define specific public and private endpoints with custom rules.
27
62
@@ -45,7 +80,7 @@ authorization:
45
80
- `privateEndpoints`: Maps regex paths to HTTP methods or `[method, scope]` tuples
46
81
- Scopes define required OAuth2 scopes for the operation
47
82
48
-
### Mode: `disabled`
83
+
#### Mode: `disabled`
49
84
50
85
No route-level authorization applied.
51
86
@@ -55,11 +90,11 @@ authorization:
55
90
mode: "disabled"
56
91
```
57
92
58
-
## Record-Level Authorization
93
+
### Record-Level Authorization
59
94
60
95
Configure via `authorization.record` section in `values.yaml`.
61
96
62
-
### Mode: `disabled` (Default)
97
+
#### Mode: `disabled` (Default)
63
98
64
99
No record-level filtering applied. All collections and items are visible to authenticated users.
65
100
@@ -69,7 +104,7 @@ authorization:
69
104
mode: "disabled"
70
105
```
71
106
72
-
### Mode: `custom`
107
+
#### Mode: `custom`
73
108
74
109
Use Python filter classes to control visibility of collections and items.
Review the stac-auth-proxy [documentation for more information on custom filters](https://developmentseed.org/stac-auth-proxy/user-guide/record-level-auth/#custom-filter-factories).
125
+
Review the stac-auth-proxy [documentation for more information on custom filters](record-level-auth.md#custom-filter-factories).
0 commit comments