Dbz 9419 add connection validator pulsar by pxcamus · Pull Request #295 · debezium/debezium-platform

pxcamus · 2026-03-11T19:27:07Z

WIP PR to add Apache Pulsar connection validation.

github-actions · 2026-03-11T21:00:55Z

Hi @pxcamus, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

mfvitale · 2026-03-12T08:46:25Z

Hi @pxcamus thanks for the PR. Could you please prefix the commit messages with debezium/dbz#1083? Thanks.

mfvitale · 2026-03-12T10:02:29Z

debezium-platform-conductor/src/main/resources/connection-schemas.json

  },
  {
-    "type": "KAFKA",
+    "type": "APACHE_PULSAR",


Why you changed the KAFKA?

My bad, I will put it back!

mfvitale

@pxcamus The general approach looks good. Let's continue with the other auth and then I'll do another review pass.

...n/java/io/debezium/platform/environment/connection/destination/pulsar/PulsarAuthHandler.java

.../java/io/debezium/platform/environment/connection/destination/PulsarConnectionValidator.java

Naros · 2026-03-16T16:26:56Z

...r/src/test/java/io/debezium/platform/environment/connection/PulsarConnectionValidatorIT.java

+    // private PulsarConnectionValidator validator;
+    //
+    // @BeforeEach
+    // void setUp() {
+    // validator = new PulsarConnectionValidator(DEFAULT_30_SECONDS_TIMEOUT);
+    // }


If this isn't needed, let's remove it.

Naros · 2026-03-16T16:27:05Z

...r/src/test/java/io/debezium/platform/environment/connection/PulsarConnectionValidatorIT.java

+        // ConnectionValidationResult result = validator.validate(connection);
+
+        // assertTrue(result.valid(), "Connection validation should succeed");


Same, remove if its no longer needed.

I finally got around to fix the tests. I will create a PulsarConnectionValidatorTest.java very soon as well, and hoping later today to add more tests for the different auth handlers.

debezium-platform-conductor/pom.xml

mfvitale · 2026-03-17T14:37:48Z

@pxcamus Could you please rebase with latest main?

pxcamus · 2026-03-17T14:47:36Z

@pxcamus Could you please rebase with latest main?

Done!

debezium-platform-conductor/pom.xml

...java/io/debezium/platform/environment/connection/destination/pulsar/PulsarAdminProvider.java

github-actions · 2026-03-18T10:58:01Z

Hi @pxcamus, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

pxcamus · 2026-03-18T20:08:23Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

mfvitale · 2026-03-19T16:05:11Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

pxcamus · 2026-03-19T20:06:50Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

mfvitale · 2026-03-20T08:17:36Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

Honestly for now I'll go with a mocked one.

pxcamus · 2026-03-25T13:18:10Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

Honestly for now I'll go with a mocked one.

@mfvitale Should the OAuth2 connection validation include the retrieval of the token? I.e. do I request the client credentials and request a token first? My concern is that the OAuth2 provider could be un-reachable from the platform conductor, right?

The other option is to just collect the token through the stage UI and validate the connection.

I have a working OAuth2 provider implementation for the integration tests, so can use the actual flow.

Naros

From my PoV, once the following is addressed then LGTM.

Naros · 2026-03-26T04:08:25Z

...io/debezium/platform/environment/connection/destination/pulsar/PulsarAuthHandlerFactory.java

+    }
+
+    public PulsarAuthHandler getAuthHandler(String authType) {
+        if (authType == null || authType.trim().isEmpty()) {


Suggested change

if (authType == null || authType.trim().isEmpty()) {

if (Strings.isNullorEmpty(authType)) {

mfvitale · 2026-03-26T14:57:01Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

Honestly for now I'll go with a mocked one.

@mfvitale Should the OAuth2 connection validation include the retrieval of the token? I.e. do I request the client credentials and request a token first? My concern is that the OAuth2 provider could be un-reachable from the platform conductor, right?

The other option is to just collect the token through the stage UI and validate the connection.

I have a working OAuth2 provider implementation for the integration tests, so can use the actual flow.

This is a good point. We should not only think about the validation phase but also what happens when a connection is then validated and used in the DS instance deployed by the platform.

@pxcamus So for now since there is no support for loading credentials file.
In https://pulsar.apache.org/docs/next/security-oauth2/ I see that the client requires to use the keyFile so I will not support it for now in the validation.

pxcamus · 2026-03-26T15:01:02Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

Honestly for now I'll go with a mocked one.

@mfvitale Should the OAuth2 connection validation include the retrieval of the token? I.e. do I request the client credentials and request a token first? My concern is that the OAuth2 provider could be un-reachable from the platform conductor, right?
The other option is to just collect the token through the stage UI and validate the connection.
I have a working OAuth2 provider implementation for the integration tests, so can use the actual flow.

This is a good point. We should not only think about the validation phase but also what happens when a connection is then validated and used in the DS instance deployed by the platform.

@pxcamus So for now since there is no support for loading credentials file. In https://pulsar.apache.org/docs/next/security-oauth2/ I see that the client requires to use the keyFile so I will not support it for now in the validation.

@mfvitale unless I missed something, it can be loaded as a base64 encoded string, right?

But to clarify, do I then wrap up the PR by passing the token for the validation?

mfvitale · 2026-03-26T15:17:04Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

Honestly for now I'll go with a mocked one.

@mfvitale Should the OAuth2 connection validation include the retrieval of the token? I.e. do I request the client credentials and request a token first? My concern is that the OAuth2 provider could be un-reachable from the platform conductor, right?
The other option is to just collect the token through the stage UI and validate the connection.
I have a working OAuth2 provider implementation for the integration tests, so can use the actual flow.

This is a good point. We should not only think about the validation phase but also what happens when a connection is then validated and used in the DS instance deployed by the platform.
@pxcamus So for now since there is no support for loading credentials file. In https://pulsar.apache.org/docs/next/security-oauth2/ I see that the client requires to use the keyFile so I will not support it for now in the validation.

@mfvitale unless I missed something, it can be loaded as a base64 encoded string, right?
But to clarify, do I then wrap up the PR by passing the token for the validation?

Where you get this infos?

pxcamus · 2026-03-26T15:19:56Z

@mfvitale If you could please take a look at the approach I used for testing JWT auth. I am going to add IT tests with expired token, etc... then switch to OAuth2. Thanks!

@pxcamus It LGTM until now. 🚀

One small question please @mfvitale : for integration tests, should I spinnup an actual OAuth2 provider, such as Keycloak or Hydra? Or mock one to return hardcoded tokens? If using an actual provider, any preference? Thanks!

Honestly for now I'll go with a mocked one.

@mfvitale Should the OAuth2 connection validation include the retrieval of the token? I.e. do I request the client credentials and request a token first? My concern is that the OAuth2 provider could be un-reachable from the platform conductor, right?
The other option is to just collect the token through the stage UI and validate the connection.
I have a working OAuth2 provider implementation for the integration tests, so can use the actual flow.

This is a good point. We should not only think about the validation phase but also what happens when a connection is then validated and used in the DS instance deployed by the platform.
@pxcamus So for now since there is no support for loading credentials file. In https://pulsar.apache.org/docs/next/security-oauth2/ I see that the client requires to use the keyFile so I will not support it for now in the validation.

@mfvitale unless I missed something, it can be loaded as a base64 encoded string, right?

But to clarify, do I then wrap up the PR by passing the token for the validation?

Where you get this infos?

https://pulsar.apache.org/docs/4.1.x/security-oauth2/

mfvitale · 2026-03-26T15:45:03Z

@mfvitale unless I missed something, it can be loaded as a base64 encoded string, right?

But to clarify, do I then wrap up the PR by passing the token for the validation?

Where you get this infos?

https://pulsar.apache.org/docs/4.1.x/security-oauth2/

Well then it should work but is not the best from the security point, since this base64 string will be then passed in the CRD definition.

Let's add the support for the validation for now.

pxcamus · 2026-03-30T15:23:47Z

@mfvitale I am done AFAIK. One question (hopefully not too stupid): when rebasing the latest main on my branch, I saw the following entry added to POM.xml:

<dependency> <groupId>io.debezium</groupId> <artifactId>debezium-connector-common</artifactId> <version>${version.debezium}</version> </dependency>

But I cannot resolve this dependency. How do I build it locally? Thanks!

pxcamus · 2026-04-01T17:23:22Z

@pxcamus Could you please check the failure?

@mfvitale I am struggling so much to run my branch to update the ITs 😅 When trying to build the project:

Downloading from confluent: https://packages.confluent.io/maven/io/debezium/debezium-quarkus-outbox/3.6.0-SNAPSHOT/debezium-quarkus-outbox-3.6.0-SNAPSHOT.jar Downloading from confluent: https://packages.confluent.io/maven/io/debezium/debezium-operator-api/3.6.0-SNAPSHOT/debezium-operator-api-3.6.0-SNAPSHOT.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 22.820 s [INFO] Finished at: 2026-04-01T19:02:04+02:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project debezium-platform-conductor: Could not resolve dependencies for project io.debezium:debezium-platform-conductor:jar:3.6.0-SNAPSHOT [ERROR] dependency: io.debezium:debezium-quarkus-outbox:jar:3.6.0-SNAPSHOT (compile) [ERROR] Could not find artifact io.debezium:debezium-quarkus-outbox:jar:3.6.0-SNAPSHOT in confluent (https://packages.confluent.io/maven/) [ERROR] dependency: io.debezium:debezium-operator-api:jar:3.6.0-SNAPSHOT (compile) [ERROR] Could not find artifact io.debezium:debezium-operator-api:jar:3.6.0-SNAPSHOT in confluent (https://packages.confluent.io/maven/)

But then when trying to build debezium-quarkus-outbox, I get an issue with something else (debezium-connector-informix). I suspect I am doing something stupid, but can't figure out what exactly...

Naros · 2026-04-02T09:38:08Z

There are now a few cross-repo dependencies, and it's probably something we should try to document clearly, particularly for first-time contributors. The debezium-quarkus repo now requires debezium-connector-informix to be built up-front. So if you clone that repository and build it, then that should solve your issue. Just be mindful that the Informix repo likely will require the main debezium/debezium repo to be built as well.

So build

debezium/debezium
debezium/debezium-connector-informix
debezium/debezium-quarkus
debezium/debezium-platform

pxcamus · 2026-04-02T09:45:40Z

There are now a few cross-repo dependencies, and it's probably something we should try to document clearly, particularly for first-time contributors. The debezium-quarkus repo now requires debezium-connector-informix to be built up-front. So if you clone that repository and build it, then that should solve your issue. Just be mindful that the Informix repo likely will require the main debezium/debezium repo to be built as well.

So build

debezium/debezium

debezium/debezium-connector-informix

debezium/debezium-quarkus

debezium/debezium-platform

Hi @Naros , I was able to resolve everything last night, except the Informix connector:

[INFO] DOCKER> [debezium/informix-test-database:15]: Created docker-build.tar in 26 milliseconds
[INFO] DOCKER> Credentials helper reply for "docker-credential-desktop" is docker-credential-osxkeychain (github.com/docker/docker-credential-helpers) v0.9.5
[ERROR] DOCKER> Unable to pull 'icr.io/informix/informix-developer-database:15.0' from registry 'icr.io' : {"message":"failed to resolve reference "icr.io/informix/informix-developer-database:15.0": icr.io/informix/informix-developer-database:15.0: not found"} (Not Found: 404) [{"message":"failed to resolve reference "icr.io/informix/informix-developer-database:15.0": icr.io/informix/informix-developer-database:15.0: not found"} (Not Found: 404)]

Naros · 2026-04-02T09:47:20Z

@pxcamus for the meantime can you try -Pinformix14 or -Pinformix12 to use the 14 or 12 images, do that work for you?

pxcamus · 2026-04-02T13:56:16Z

@pxcamus for the meantime can you try -Pinformix14 or -Pinformix12 to use the 14 or 12 images, do that work for you?

That worked, thanks!

pxcamus · 2026-04-02T14:49:05Z

@pxcamus for the meantime can you try -Pinformix14 or -Pinformix12 to use the 14 or 12 images, do that work for you?

@Naros actually a few more issues but on macOS ARM. the debezium-quarkus-testsuite-deployment produces a test JAR. So I could not run mvn install -Dmaven.test.skip=true. But when trying to skip just the execution of tests with mvn install -DskipTests I am getting this error:

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.48.0:start (start-mongodb) on project debezium-quarkus-mongodb-integration-tests: I/O Error: Unable to pull 'quay.io/debezium/mongo:6.0' from registry 'quay.io' : {"message":"no matching manifest for linux/arm64/v8 in the manifest list entries: no match for platform in manifest: not found"} (Not Found: 404) -> [Help 1]

I tried everything I could think of: setting up a default profile in ~/.m2/settings.xml:

<profiles> <profile> <id>default</id> <properties> <docker.host>unix://${user.home}/.docker/run/docker.sock</docker.host> <docker.platform>linux/amd64</docker.platform> </properties> </profile> </profiles>

I downloaded the image before running the Maven command:

docker pull --platform linux/amd64 quay.io/debezium/mongo:6.0

Then tried passing in various way a flag: DOCKER_DEFAULT_PLATFORM=linux/amd64 mvn install -DskipTests.

I think next I will have to modify the POM files to pass <platform>${docker.platform}</platform>.

Good news is that I am saving to buy a Linux workstation 😅

mfvitale · 2026-04-02T15:02:57Z

@pxcamus snapshots should now be published on maven central so you could just try to run test on your branch and dependencies should be resolved.

pxcamus · 2026-04-02T15:08:06Z

@pxcamus snapshots should now be published on maven central so you could just try to run test on your branch and dependencies should be resolved.

Still seeing this @mfvitale :

[ERROR] Failed to execute goal on project debezium-platform-conductor: Could not resolve dependencies for project io.debezium:debezium-platform-conductor:jar:3.6.0-SNAPSHOT [ERROR] dependency: io.debezium:debezium-operator-api:jar:3.6.0-SNAPSHOT (compile) [ERROR] Could not find artifact io.debezium:debezium-operator-api:jar:3.6.0-SNAPSHOT in confluent (https://packages.confluent.io/maven/)

vsantonastaso · 2026-04-02T15:31:23Z

@pxcamus for the meantime can you try -Pinformix14 or -Pinformix12 to use the 14 or 12 images, do that work for you?

@Naros actually a few more issues but on macOS ARM. the debezium-quarkus-testsuite-deployment produces a test JAR. So I could not run mvn install -Dmaven.test.skip=true. But when trying to skip just the execution of tests with mvn install -DskipTests I am getting this error:

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.48.0:start (start-mongodb) on project debezium-quarkus-mongodb-integration-tests: I/O Error: Unable to pull 'quay.io/debezium/mongo:6.0' from registry 'quay.io' : {"message":"no matching manifest for linux/arm64/v8 in the manifest list entries: no match for platform in manifest: not found"} (Not Found: 404) -> [Help 1]

I tried everything I could think of: setting up a default profile in ~/.m2/settings.xml:

<profiles> <profile> <id>default</id> <properties> <docker.host>unix://${user.home}/.docker/run/docker.sock</docker.host> <docker.platform>linux/amd64</docker.platform> </properties> </profile> </profiles>

I downloaded the image before running the Maven command:

docker pull --platform linux/amd64 quay.io/debezium/mongo:6.0

Then tried passing in various way a flag: DOCKER_DEFAULT_PLATFORM=linux/amd64 mvn install -DskipTests.

I think next I will have to modify the POM files to pass <platform>${docker.platform}</platform>.

Good news is that I am saving to buy a Linux workstation 😅

Hi @pxcamus,
The ~/.m2/settings.xml approach couldn't work because docker-maven-plugin doesn't
automatically inherit properties from there.
You could try with:

Add <docker.platform>linux/amd64</docker.platform> to the properties section
Add ${docker.platform} inside each block
run mvn command with -Ddocker.platform. e.g. mvn clean install -Ddocker.platform=linux/amd64

Ah for sure you have to enable Rosetta emulation in your docker engine

pxcamus · 2026-04-02T16:17:34Z

Thanks @vsantonastaso , that's what I thought I would have to do, but @mfvitale helped me out, and I was able to build.

Signed-off-by: Philippe Camus <pxcamus@pm.me>

…min` integration and improved error handling. Update dependencies for Pulsar and Debezium. Signed-off-by: Philippe Camus <pxcamus@pm.me>

… validation using Testcontainers Signed-off-by: Philippe Camus <pxcamus@pm.me>

…emes through `PulsarAuthHandler` abstraction Signed-off-by: Philippe Camus <pxcamus@pm.me>

… `JwtAuthHandler` implementation and enhance connection validation logic Signed-off-by: Philippe Camus <pxcamus@pm.me>

…inProvider` interfaces to document authentication configuration and builder abstraction Signed-off-by: Philippe Camus <pxcamus@pm.me>

…s and minor code formatting adjustments Signed-off-by: Philippe Camus <pxcamus@pm.me>

…tion in interface Signed-off-by: Philippe Camus <pxcamus@pm.me>

…rFactory` and comprehensive unit tests for Pulsar authentication handlers. Signed-off-by: Philippe Camus <pxcamus@pm.me>

…tion with JWT authentication and enhance test coverage. Signed-off-by: Philippe Camus <pxcamus@pm.me>

… scenarios for expired JWT tokens and inject missing `authScheme` configuration. Add constant for JWT token secret key. Signed-off-by: Philippe Camus <pxcamus@pm.me>

…uth2AuthHandler` and extend connection validation tests with integration support Signed-off-by: Philippe Camus <pxcamus@pm.me>

…ort order inconsistencies, and include missing license headers in Pulsar-related classes and tests Signed-off-by: Philippe Camus <pxcamus@pm.me Signed-off-by: Philippe Camus <pxcamus@pm.me>

…ence correct Apache Software License version Signed-off-by: Philippe Camus <pxcamus@pm.me>

…Test` to reflect authority component validation in service URI. Signed-off-by: Philippe Camus <pxcamus@pm.me>

…ion tests to provide more specific failure reasons Signed-off-by: Philippe Camus <pxcamus@pm.me>

pxcamus mentioned this pull request Mar 11, 2026

Add connection validator for Apache Pulsar [DBZ-9419] debezium/dbz#1083

Open

pxcamus force-pushed the DBZ-9419-add-connection-validator-pulsar branch from 3d17fb9 to 1ef50b0 Compare March 12, 2026 09:13

mfvitale reviewed Mar 12, 2026

View reviewed changes

Naros requested changes Mar 16, 2026

View reviewed changes

pxcamus force-pushed the DBZ-9419-add-connection-validator-pulsar branch from 528da49 to 53812e8 Compare March 17, 2026 14:46

pxcamus requested a review from Naros March 17, 2026 15:30

mfvitale reviewed Mar 18, 2026

View reviewed changes

debezium-platform-conductor/pom.xml Outdated Show resolved Hide resolved

mfvitale reviewed Mar 18, 2026

View reviewed changes

debezium-platform-conductor/pom.xml Outdated Show resolved Hide resolved

mfvitale reviewed Mar 18, 2026

View reviewed changes

...java/io/debezium/platform/environment/connection/destination/pulsar/PulsarAdminProvider.java Outdated Show resolved Hide resolved

pxcamus force-pushed the DBZ-9419-add-connection-validator-pulsar branch from 11667a4 to f58ffe3 Compare March 18, 2026 11:02

Naros reviewed Mar 26, 2026

View reviewed changes

pxcamus force-pushed the DBZ-9419-add-connection-validator-pulsar branch from 266eff9 to b75c041 Compare March 30, 2026 15:08

pxcamus requested a review from Naros March 30, 2026 15:21

pxcamus force-pushed the DBZ-9419-add-connection-validator-pulsar branch 2 times, most recently from b00b1ea to 0db866b Compare March 31, 2026 14:07

mfvitale mentioned this pull request Apr 2, 2026

Debezium Platform cannot resolve snapshot dependencies debezium/dbz#1783

Open

pxcamus added 16 commits April 2, 2026 20:43

debezium/dbz#1083: Scaffold Pulsar connection validator

fbb2172

Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Enhance Pulsar connection validator with `PulsarAd…

5926e4a

…min` integration and improved error handling. Update dependencies for Pulsar and Debezium. Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add integration tests for Apache Pulsar connection…

e07a526

… validation using Testcontainers Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add support for multiple Pulsar authentication sch…

96a691a

…emes through `PulsarAuthHandler` abstraction Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Introduce JWT-based authentication for Pulsar with…

f582600

… `JwtAuthHandler` implementation and enhance connection validation logic Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add Javadoc for PulsarAuthHandler and `PulsarAdm…

47c2a6e

…inProvider` interfaces to document authentication configuration and builder abstraction Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add missing license headers to Pulsar-related file…

32142a1

…s and minor code formatting adjustments Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Update dependency from to and adjust author annota…

de633d4

…tion in interface Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add validation for authType in `PulsarAuthHandle…

3e5d615

…rFactory` and comprehensive unit tests for Pulsar authentication handlers. Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add integration tests for Pulsar connection valida…

c2e94bc

…tion with JWT authentication and enhance test coverage. Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Extend Pulsar connection validation tests to cover…

4055930

… scenarios for expired JWT tokens and inject missing `authScheme` configuration. Add constant for JWT token secret key. Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add OAuth2-based authentication for Pulsar via `OA…

8d9830c

…uth2AuthHandler` and extend connection validation tests with integration support Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Add minor code formatting adjustments, resolve imp…

3be0454

…ort order inconsistencies, and include missing license headers in Pulsar-related classes and tests Signed-off-by: Philippe Camus <pxcamus@pm.me Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Update license header in JwtAuthHandler to refer…

f2d060c

…ence correct Apache Software License version Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Update error message in `PulsarConnectionValidator…

99d1ebf

…Test` to reflect authority component validation in service URI. Signed-off-by: Philippe Camus <pxcamus@pm.me>

debezium/dbz#1083: Update error messages in Pulsar connection validat…

2e25131

…ion tests to provide more specific failure reasons Signed-off-by: Philippe Camus <pxcamus@pm.me>

pxcamus force-pushed the DBZ-9419-add-connection-validator-pulsar branch from 458c73f to 2e25131 Compare April 2, 2026 18:43

		// ConnectionValidationResult result = validator.validate(connection);

		// assertTrue(result.valid(), "Connection validation should succeed");

	if (authType == null \|\| authType.trim().isEmpty()) {
	if (Strings.isNullorEmpty(authType)) {

Uh oh!

Conversation

pxcamus commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 11, 2026

Uh oh!

mfvitale commented Mar 12, 2026

Uh oh!

mfvitale Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

pxcamus Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

mfvitale left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Naros Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

Naros Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

pxcamus Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mfvitale commented Mar 17, 2026

Uh oh!

pxcamus commented Mar 17, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Mar 18, 2026

Uh oh!

pxcamus commented Mar 18, 2026

Uh oh!

mfvitale commented Mar 19, 2026

Uh oh!

pxcamus commented Mar 19, 2026

Uh oh!

mfvitale commented Mar 20, 2026

Uh oh!

pxcamus commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Naros left a comment

Choose a reason for hiding this comment

Uh oh!

Naros Mar 26, 2026

Choose a reason for hiding this comment

Uh oh!

mfvitale commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pxcamus commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mfvitale commented Mar 26, 2026

Uh oh!

pxcamus commented Mar 26, 2026

Uh oh!

mfvitale commented Mar 26, 2026

Uh oh!

pxcamus commented Mar 30, 2026

Uh oh!

pxcamus commented Apr 1, 2026

Uh oh!

Naros commented Apr 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pxcamus commented Apr 2, 2026

Uh oh!

Naros commented Apr 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pxcamus commented Mar 11, 2026 •

edited

Loading

pxcamus commented Mar 25, 2026 •

edited

Loading

mfvitale commented Mar 26, 2026 •

edited

Loading

pxcamus commented Mar 26, 2026 •

edited

Loading

Naros commented Apr 2, 2026 •

edited

Loading

Naros commented Apr 2, 2026 •

edited

Loading