Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to ValidateDomain),

mjurczyk
mjurczyk
Community Member
in SCIM Bridge

Tried updating SCIM Bridge to 2.0.... getting a bunch of errors.

Used script to reconfigure docker compose

scim_1 | 9:07PM INF 1Password SCIM bridge, starting up application=op-scim version=2.0.0 scim_1 | 9:07PM INF registering new health component application=op-scim component=RedisCache service=health version=2.0.0 scim_1 | 9:07PM INF starting to poll components for health reports application=op-scim service=health version=2.0.0 scim_1 | 9:07PM ??? Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to GetCache), Network: (failed to NewRedisConnPool), cannot initialize connection: cannot connect to redis: dial tcp 172.21.0.2:6379: connect: connection refused application=op-scim version=2.0.0 scim_1 | 9:08PM INF 1Password SCIM bridge, starting up application=op-scim version=2.0.0 scim_1 | 9:08PM INF registering new health component application=op-scim component=RedisCache service=health version=2.0.0 scim_1 | 9:08PM INF starting to poll components for health reports application=op-scim service=health version=2.0.0 scim_1 | 9:08PM INF registering new health component application=op-scim component=SCIMServer service=health version=2.0.0 scim_1 | 9:08PM ??? Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to ValidateDomain), domain invalid application=op-scim version=2.0.0 scim_1 | 9:08PM INF 1Password SCIM bridge, starting up application=op-scim version=2.0.0 scim_1 | 9:08PM INF registering new health component application=op-scim component=RedisCache service=health version=2.0.0 scim_1 | 9:08PM INF starting to poll components for health reports application=op-scim service=health version=2.0.0 scim_1 | 9:08PM INF registering new health component application=op-scim component=SCIMServer service=health version=2.0.0 scim_1 | 9:08PM ??? Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to ValidateDomain), domain invalid application=op-scim version=2.0.0 scim_1 | 9:08PM INF 1Password SCIM bridge, starting up application=op-scim version=2.0.0 scim_1 | 9:08PM INF registering new health component application=op-scim component=RedisCache service=health version=2.0.0 scim_1 | 9:08PM INF starting to poll components for health reports application=op-scim service=health version=2.0.0 scim_1 | 9:08PM INF registering new health component application=op-scim component=SCIMServer service=health version=2.0.0 scim_1 | 9:08PM ??? Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to ValidateDomain), domain invalid application=op-scim version=2.0.0 redis_1 | 1:C 15 Apr 2021 21:07:58.828 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis_1 | 1:C 15 Apr 2021 21:07:58.828 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started redis_1 | 1:C 15 Apr 2021 21:07:58.828 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf redis_1 | 1:M 15 Apr 2021 21:07:58.832 * Running mode=standalone, port=6379. redis_1 | 1:M 15 Apr 2021 21:07:58.832 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. redis_1 | 1:M 15 Apr 2021 21:07:58.832 # Server initialized redis_1 | 1:M 15 Apr 2021 21:07:58.833 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis_1 | 1:M 15 Apr 2021 21:07:58.833 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. redis_1 | 1:M 15 Apr 2021 21:07:58.833 * Ready to accept connections compose_scim_1 exited with code 1 compose_scim_1 exited with code 1 compose_scim_1 exited with code 1 compose_scim_1 exited with code 1 scim_1 | 9:09PM ??? Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to ValidateDomain), domain invalid application=op-scim version=2.0.0

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: DOCKER
Referrer: forum-search:Server: (failed to run 1Password SCIM bridge), Wrapped: (failed to ValidateDomain), domain invalid application=op-scim version=2.0.0

Comments

  • mjurczyk
    mjurczyk
    Community Member

    Got it.

  • 1P_Amanda
    1P_Amanda

    Awesome! Do you mind sharing what you did so someone else who runs into the issue might have an idea what to change?

    Cheers!
    Amanda

  • austim
    austim
    Community Member

    I removed the scim load balancer from the workloads that was left over, then redeployed and was fine. Make sure you've removed all previous deployment artifacts before install anew. That's what worked for me.

  • 1P_Amanda
    1P_Amanda

    Thank you for sharing!

This discussion has been closed.