Search
-
Re: Azure Kubernetes Service deployment issue "http: TLS handshake error from
: : EOF" 
Hi Amanda, I'm not to familiar with Kubernetes but what i can tell is that port 443 ad 80 are open. DSN entry is set to LoadBalancer Ingress address. (i blurred out the public ip address) -
SCIM provisioning not recognizing WAN IP?
I've followed the guide for deploying the SCIM bridge to Azure, and have completed the steps up to adding the WAN IP to DNS. As far as I can tell, the Kubernetes service is running correctly. Using "kubectl get services" I've pulled the loadbalancer IP and added as a A record in our DNS with no luck. Besides fat-fingering… -
Azure Kubernetes and SSL Cert Error after fresh deployment
Hello, I tried to deploy the scim bridge in Azure Kubernetes. I followed the guide here https://support.1password.com/scim-deploy-azure/. DNS A record is pointing to the loadbalancer ip. But when I try to connect to the dns name I get an error that seems to me like there is no certificate deployed: ERR_SSL_PROTOCOL_ERROR… -
SCIM container on AWS ECS behind ALB
We are trying to run the SCIM container on ECS behind a loadbalancer. * We are able to bring the container up and access the setup. The setup starts on 3002 port and as we login to 1password and install scimsession file, the setup server stops and restarts on some other port (8443). How to avoid that? * As this is behind… -
Re: SCIM - Kubernetes Setup
@cohix it appears that the 32361 and 30092 are the nodeports that are assigned to the LoadBalancer. When i run kubectl describe service op-scim, it does show the target ports are set to 8443 and 8080. I've pretty much run the exact manifest files defined in the github example page that you linked, only changing…
5 results