Skip to content

Commit fba5561

Browse files
committed
fix: add allowPublicKeyRetrieval to OMS datasource for MySQL 8.0 compat
MySQL 8.0 uses caching_sha2_password by default, which requires allowPublicKeyRetrieval=true when useSSL=false. The handshake matching test still works because the two pools differ in username and database.
1 parent bd64f05 commit fba5561

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

mysql-dual-conn/src/main/resources/application.properties

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
server.port=8080
22

33
# --- OMS DataSource (primary) ---
4-
datasource.oms.jdbc-url=jdbc:mysql://localhost:3306/myntra_oms?useSSL=false
4+
datasource.oms.jdbc-url=jdbc:mysql://localhost:3306/myntra_oms?useSSL=false&allowPublicKeyRetrieval=true
55
datasource.oms.username=omsAppUser
66
datasource.oms.password=omsPassword
77
datasource.oms.driver-class-name=com.mysql.cj.jdbc.Driver
88

9-
# --- Camunda DataSource (secondary, different user & capability flags) ---
10-
# allowPublicKeyRetrieval=true causes different MySQL capability flags,
11-
# which is the key condition that triggers the multi-handshake matching bug.
9+
# --- Camunda DataSource (secondary, different user & database) ---
10+
# Different username + database is the key condition that triggers the
11+
# multi-handshake matching bug during Keploy replay.
1212
datasource.camunda.jdbc-url=jdbc:mysql://localhost:3306/camunda?useSSL=false&allowPublicKeyRetrieval=true
1313
datasource.camunda.username=stagebuster
1414
datasource.camunda.password=camundaPassword

0 commit comments

Comments
 (0)