option(OracleR2dbcOptions.TLS_SERVER_DN_MATCH, "false") does not work about oracle-r2dbc

[Michael-A-McMahon]

Thank you for showing me this. It definitely looks like a bug :(
I'll have time to debug tomorrow. I'll update once I learn more...

[Michael-A-McMahon]

I've found the root cause:
Oracle JDBC enables DN matching by default when using a URL of the form: jdbc:oracle:thin:@tcps:...
Oracle R2DBC uses this form of URL when ConnectionFactoryOptions.SSL is set to true.

In Oracle R2DBC 1.0.0, we can work around this by configuring a descriptor with PROTOCOL=TCPS:

    ConnectionFactoryOptions options =
      ConnectionFactoryOptions.builder()
        .option(ConnectionFactoryOptions.DRIVER, "oracle")
        .option(OracleR2dbcOptions.DESCRIPTOR,
          "(DESCRIPTION=" +
            "(ADDRESS=(PROTOCOL=TCPS)(HOST=your.db.host.com)(PORT=1522))" +
            "(CONNECT_DATA=(SERVICE_NAME=your.db.service.name)))")
        .option(ConnectionFactoryOptions.USER, "...")
        .option(ConnectionFactoryOptions.PASSWORD, "...")
        .build();

For the next release, I will fix this so that we don't need the work around.

[sourabhdug]

Thank you @Michael-A-McMahon I will try the work around, that would be definitely better than having to specify the entire DN!