Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
5 years agoUsers in Okta to 1password groups not syncing
Users in Okta to 1password groups not syncing
{"level":"info","version":"2.1.0","build":"201001","application":"op-scim","component":"SCIMServer","request_id":"c5sli21dq3sf0bdhs7v0","group":"i7xsp...
Former Member
5 years agoHi @varun118.
Thank you for confirming the open ports.
Based on your earlier message it sounds like you are running the SCIM bridge behind a load balancer (ELB) that is already doing TLS termination (using an AWS certificate). If this is the case then you will not need the SCIM bridge to obtain its own certificate.
You can override the default behaviour of the SCIM bridge by setting the following environment variables for the SCIM bridge:
* OP_LETSENCRYPT_DOMAIN to an empty string (""). This will prevent the SCIM bridge from trying to obtain a certificate from Let's Encrypt.
* OP_PORT to the port you have configured the load balancer to use to forward traffic to the SCIM bridge, such as 80 or 8080 for example. This changes the listening port of the SCIM bridge when not using LetsEncrypt TLS, and it defaults to 3002.
Note that both of these variables can also be passed to the SCIM bridge as command line arguments, --letsencrypt-domain and --port respectively.