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:
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.
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
Hi @rnowling-memphis I've added the option to send it as a query param rather than inside the username.
It is already on the master branch and will be released on the coming release
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:
https://region.cloud.memphis.dev/122222/produce/topic
orhttps://region.cloud.memphis.dev/produce/topic/122222