Do not disable certificate verification connecting to Redis

[enerdgumen]

Related to:

• DO-1331 Redis - Certificato SSL non correttamente verificato
• MOTOR-1735 Update Redis 6 domain configuration and SSL settings

[cpiemontese]

Do you need a new release ASAP or do you want to test by pointing to master?

[enerdgumen]

We are not sure whether to apply these changes before or after fixing the Redis settings (see comments in card).

@primait/shared-services do you have an opinion about this?

[cpiemontese]

We could wait a bit and merge/release after you fix the Redis settings, but even if we did everything before I don't think you'd be losing out on patches or something like that...

[enerdgumen]

do you want to test by pointing to master?

I tested this settings on staging and everything is ok:

iex(atreyu@atreyu-web-deployment-f678b8bf9-86vqm)13> {:ok, r} = Redix.start_link("redis://atreyu:***redacted***@master.redis-staging-cluster.oznmfz.euw1.cache.amazonaws.com/46", ssl: true, socket_opts: [ customize_hostname_check: [ match_fun: :public_key.pkix_verify_hostname_match_fun(:https) ] ] )
{:ok, #PID<0.8840.0>}

iex(atreyu@atreyu-web-deployment-f678b8bf9-86vqm)14> Redix.command(r, ["get", "prima_auth0_ex_tokens:atreyu:peano"]) 
{:ok, "06aXrrIwQVf0Wp2BRuefa3hmfuBqG78mcmnQkyv69lt5T..."}

I don't think you'd be losing out on patches or something like that

Ok, since there isn't any shortcoming I would say to release it before fixing the settings, so that we will fix the security issue in one shot.
It's not urgent for us. Just keep in mind that this is now a requirement for our task, planned for the next sprint. 🙂