memphisdev / memphis-rest-gateway Goto Github PK

Hi Memphis.dev team,

Firstly, thank you for your hard work on the Debezium + Memphis tutorial and examples. I've been using it for Change Data Capture (CDC) and it's been immensely beneficial.

I've been perusing the REST API documentation, and I've run into a bit of an obstacle. Currently, I cannot find any documentation or references that specify how to pass the Producer name as a parameter. I'm hoping to use this function in my project, so clarification would be really valuable to me.

Could you kindly provide me with some guidance on this? Is it possible to pass the Producer name as a parameter, or perhaps it's a functionality that isn't currently supported or is not documented?

Thank you in advance for your time and support. I look forward to hearing from you soon.

Best regards,
Andrea

Description

Currently (v1.2.0), the only supported authentication method is using JWT.
While it is a standard for most use cases, not all systems support refreshing tokens nor concat a JWT token as a header.
Therefore, a second authentication method should be available to support the rest of the use cases in the shape of Access keys.

This feature contains:

• Adding support in access keys creation.
• Adding key management ability to the Web Console in the Users section.
• Add interpretation of access keys when interacting with the REST Gateway.

Problem:
Memphis Cloud requires passing an account id along with the username and password. The account id field is not a standard field of authorization endpoints, however, and is not likely to be supported by all external services.

User Impact:
This recently caused pain for a user who was attempting to use Debezium with Memphis Cloud.

Suggested solutions:
There are several possible solutions that maintain backwards compatibility including:

1. Combine the user and account id into a single string that is passed as the username. For example, "rj$122222" is passed as the username to the authorization endpoint.
2. Include the account id in the URL. E.g., https://region.cloud.memphis.dev/122222/produce/topic or https://region.cloud.memphis.dev/produce/topic/122222