Karthees Kalidass

Currently we support AMQP 1.0 and Kafka support is in progress. In the process to support Kafka, we have refactored our APIs to be protocol agnostic and also configurable at...

Currently _device-id_ template configuration supports placeholders namely `{{subject-cn}}` and `{{subject-dn}}`. I think it's good to support also another subjectDN's attribute _Organizational Unit Name_ (`{{subject-ou}}`). We can make the _auth-id_ template...

> With the former I disagree. FMPOV the opposite is true, i.e. when a new certificate is being issued to _the same_ device, then the values for the place holders...

@sophokles73 As we discussed, I added a new field `generated-auth-id` now to support the auth id template feature in JDBC and MongoDB registries. Also the _get credentials operation_ has been...

@sophokles73 FMPOV it is not worth the effort considering the change and what value it brings. I would also postpone it to another time.

@dejanb I would like to start with #1864 which aims to provide support for _basic authentication_. As I understood from the last meeting, that this pluggable authentication handler that is...

@dejanb Thank you, I will take a look.

@lhotari Would you mind creating a separate PR for the last 2 commits (Include `hono-service-device-registry-jdbc image in pushed images` & `tenantAdapterStore should use tenantsProperties().getAdapter()`)? One is a bug and the...

> @kaniyan thanks for the feedback. I moved those commits out to new PRs #2321 and #2322 as you have suggested. Thank your for those PRs and they have been...

>>it seems that it is a kind of formal identifier but not formal enough to actually rely on/use it. So we either omit this or define stable error codes that...