-
Notifications
You must be signed in to change notification settings - Fork 43
option(OracleR2dbcOptions.TLS_SERVER_DN_MATCH, "false") does not work #102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you for showing me this. It definitely looks like a bug :( |
I've found the root cause: In Oracle R2DBC 1.0.0, we can work around this by configuring a descriptor with 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. |
Thank you @Michael-A-McMahon I will try the work around, that would be definitely better than having to specify the entire DN! |
Above results in an error of the following trace
however adding
with expected DN causes the query and connection to succeed!
Dependencies
Oracle Version
The text was updated successfully, but these errors were encountered: