Hello,
i'm trying to deploy op-scim-helm chart on a Kubernetes GKE cluster with an external LoadBalancer and Traefikee as ingress controller.
The certificate is correctly configured with the ingress route.
But during the setup , i'm blocked with thiss error message :
ERR failed to get TLS config error="Network: (certificate manager failed to get certificate), : obtaining certificate: [] Obtain: subject does not qualify for a public certificate: " application=op-scim build=207031 version=2.7.3
I tryed to disable LE adding this env var : OP_LETSENCRYPT_DOMAIN="" but no improvement .
I configured the deployment as below :
...
- command:
- /op-scim/op-scim
env:
- name: OP_PORT
value: "8080"
- name: OP_SESSION
value: /home/opuser/.op/scimsession
- name: OP_WORKSPACE_SETTINGS
value: /home/opuser/.op/workspace-settings.json
- name: OP_WORKSPACE_CREDENTIALS
value: /home/opuser/.op/workspace-credentials.json
- name: OP_REDIS_URL
value: redis://onepwd-cc-redis-master:6379
- name: OP_PING_SERVER
value: "true"
- name: OP_LETSENCRYPT_DOMAIN
image: 1password/scim:v2.7.3
Somebody has already encounter this type of issue ?
Thank you for your help.
Best.
Ch.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Kubernetes 1.22
Browser:_ Chrome
Comments
Team Member
Hi @cdesaintleger:
Looking at your deployment configuration, to confirm, did you unset
OP_LETSENCRYPT_DOMAIN
, or did you set it to the value of""
? 1Password SCIM Bridge will skip provisioning a certificate if the value ofOP_LETSENCRYPT_DOMAIN
is set specifically to""
. Let me know.Jack
Hello @Jack.P_1P ,
Yes i can confirm you that the env var is set with an empty string
And the complete logs remains :
Hello @Jack.P_1P ,
I resolved the issue keeping the env var OP_LETSENCRYPT_DOMAIN with an empty string and set the other var OP_DOMAIN.
But on a fresh installation ( tested 2 times on dev and prod env ) , we must restart the pod 1 time to works properly. Maybe the configuration is not correctly loaded the first pod start ? i don't know.
For me this issue is resolved.
Thank you for your help.
Best regards,
Ch.