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
This is to configure envoy for end-to-end HTTP/2 required by zitadel management API. zitadel API bugs with self-signed certificates.
65
+
For publicly trusted certificates, enable TLS by updating env vars in ZITADEL.
66
+
67
67
```sh
68
-
go run ./internal/stack/configure/...
68
+
docker compose up -d
69
69
```
70
70
71
-
The above go code creates, among others, an OIDC client which pgo uses for authN/authZ. Any OIDC compliant Identity Provider (eg , Keycloak, Auth0) can be used; pgo just needs the client credentials.
71
+
Check zitadel health with `curl http://iam.192-168-0-10.sslip.io/debug/healthz` or `docker exec -it edge_edge_1 /edge healthz`
72
+
73
+
#### Use the centralized IdP for authorization in Postgres via `pgo rest` (PostgREST API) as well as minio-s3, NATS etc
72
74
73
-
Once ZITADEL is configured, revert the ports (use 80 for envoy), and `docker compose down && docker compose up -d`
75
+
edge so far creates the clients. a bit works needed to for configuring consumers of client secrets.
76
+
For now, isit ZITADEL UI (eg at http://iam.192-168-0-10.sslip.io), login (see docker-compose.yaml) and regenerate client-secrets for oauth2-proxy and minio clients in edge project. Then
74
77
75
-
Visit ZITADEL UI (eg at http://iam.192-168-0-121.sslip.io), login (see docker-compose.yaml) and regenerate client-secret for oauth2-proxy client in edge project. Then update `internal/stack/pgo/config.yaml` with the values. Again, `docker compose down && docker compose up -d`
78
+
- update `internal/stack/pgo/config.yaml` with the values
79
+
- update relevant env vars in minio container
80
+
81
+
And `docker compose down && docker compose up -d`
76
82
77
83
#### `pgo rest`: PostgREST-compatible REST API
78
84
@@ -98,13 +104,16 @@ GRANT ALL ON iam.users to anon;
98
104
Now we can GET, POST, PATCH, DELETE on the users table in iam schema like:
99
105
100
106
```sh
101
-
curl http://api.127-0-0-1.sslip.io/iam/users
107
+
curl http://api.192-168-0-10.sslip.io/iam/users
102
108
```
103
109
104
110
##### `pgo pipeline`: Debezium-compatible CDC for realtime-event/replication etc
105
111
106
112
The demo pgo-pipeline container syncs users from auth-db (in projections.users14 table) to app-db (in iam.users)
107
113
114
+
#### minio-s3
115
+
ensure minio MINIO_IDENTITY_OPENID_CLIENT_ID and MINIO_IDENTITY_OPENID_CLIENT_SECRET are set withc appropriate values. console ui is at http://minio.192-168-0-10.sslip.io.
116
+
108
117
### Kubernetes
109
118
If you already have a live k8s cluster, great just copy-paste-enter.
110
119
For development and lightweight prod, [k3s](https://github.com/k3s-io/k3s) seems a great option.
0 commit comments