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
Currently app UI config for auth has to done via environment vars.
It would be great if it could be exposed easily.
Perhaps with common configuration: Google, Microsoft, GitHub authentication packages up as a template where you just have to add your client secret and key and it'll just work.
Should also have Keycloak config as it's pretty popular.
Here is a very large spec.
apiVersion: temporal.io/v1beta1kind: TemporalClustermetadata:
name: temporalspec:
admintools:
enabled: trueimage: temporalio/admin-toolsresources: {}authorization:
# Uncomment once claims are setup in keycloak# authorizer: default# claimMapper: defaultjwtKeyProvider:
keySourceURIs:
- CHANGE_MErefreshInterval: 30m0spermissionsClaimName: permissionsimage: temporalio/serverjobResources: {}jobTtlSecondsAfterFinished: 300log:
development: falseformat: jsonlevel: infooutputFile: ""stdout: truemTLS:
certificatesDuration:
clientCertificates: 17520h0m0sfrontendCertificate: 17520h0m0sintermediateCAsCertificates: 17520h0m0sinternodeCertificate: 17520h0m0srootCACertificate: 27520h0m0sfrontend:
enabled: trueinternode:
enabled: trueprovider: cert-managerrefreshInterval: 72h0m0s # I do not think these are being considered properly.renewBefore: 1h10m0s # This toometrics:
enabled: trueprometheus:
listenAddress: ""listenPort: 9090scrapeConfig:
annotations: falseserviceMonitor:
enabled: truenumHistoryShards: 1persistence:
defaultStore:
name: defaultpasswordSecretRef:
key: passwordname: temporal-postgres-appskipCreate: falsesql:
connectAddr: temporal-postgres-rw:5432connectProtocol: tcpdatabaseName: temporalmaxConnLifetime: 0smaxConns: 0maxIdleConns: 0pluginName: postgrestaskScanPartitions: 0user: temporalvisibilityStore:
name: visibilitypasswordSecretRef:
key: passwordname: temporal-postgres-appskipCreate: falsesql:
connectAddr: temporal-postgres-rw:5432connectProtocol: tcpdatabaseName: temporal_visibilitymaxConnLifetime: 0smaxConns: 0maxIdleConns: 0pluginName: postgrestaskScanPartitions: 0user: temporalservices:
frontend:
overrides:
deployment:
spec:
template:
spec:
containers:
- name: serviceargs: ["--allow-no-auth"]httpPort: 7243membershipPort: 6933port: 7233replicas: 1resources: {}history:
httpPort: 0membershipPort: 6934port: 7234replicas: 1resources: {}matching:
httpPort: 0membershipPort: 6935port: 7235replicas: 1resources: {}worker:
httpPort: 0membershipPort: 6939port: 7239replicas: 1resources: {}ui:
enabled: trueimage: temporalio/uiingress:
annotations:
external-dns.alpha.kubernetes.io/cloudflare-proxied: "false"# this will need to be true when we are out of the basementcert-manager.io/issuer: letsencrypt-prodnginx.ingress.kubernetes.io/proxy-buffer-size: 128khosts:
- CHANGEMEtls:
- hosts:
- CHANGEMEsecretName: temporal-ingress-certoverrides:
deployment:
spec:
template:
spec:
containers:
- env:
- name: TEMPORAL_AUTH_ENABLEDvalue: "true"
- name: TEMPORAL_AUTH_SCOPESvalue: openid email profilename: uiresources: {}envFrom:
- secretRef:
name: temporal-oidc-clientreplicas: 1resources:
limits:
cpu: "1"memory: 256Mirequests:
cpu: 10mmemory: 20Miversion: 2.26.1version: 1.22.7
The text was updated successfully, but these errors were encountered:
Currently app UI config for auth has to done via environment vars.
It would be great if it could be exposed easily.
Perhaps with common configuration: Google, Microsoft, GitHub authentication packages up as a template where you just have to add your client secret and key and it'll just work.
Should also have Keycloak config as it's pretty popular.
Here is a very large spec.
The text was updated successfully, but these errors were encountered: