Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action output to external HTTP server - authorization header issue #12889

Closed
pycan-jouza opened this issue Apr 16, 2024 · 2 comments · Fixed by #12948
Closed

Action output to external HTTP server - authorization header issue #12889

pycan-jouza opened this issue Apr 16, 2024 · 2 comments · Fixed by #12948
Assignees
Labels

Comments

@pycan-jouza
Copy link

What happened?

I've got a flow that based on incoming topic message notifies external HTTP server. The problem is with authorization header. Upon saving the header value, the value turns to ******.

image

I thought this is just the security feature of the web UI to not expose any sensitive values. After crazy amount of hours debugging, I've found out that the header value ACTUALLY is ******. That's what's being sent to external server. Naturally, the authentication always fails.

What did you expect to happen?

Header value that user entered should be used, not ******.

How can we reproduce it (as minimally and precisely as possible)?

No response

Anything else we need to know?

No response

EMQX version

version
5.6.0

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

Log files

@keynslug
Copy link
Contributor

Hi @pycan-jouza, thanks for reporting.

I can confirm that this currently happens when one makes changes to the existing HTTP connector (or Webhook) configuration that already has some sensitive header configured. We'll work on the fix, but in the meantime you could try to resupply the authorization header value during editing, or conduct changes through the API.

@thalesmg thalesmg self-assigned this Apr 29, 2024
@thalesmg thalesmg linked a pull request Apr 29, 2024 that will close this issue
9 tasks
@thalesmg
Copy link
Contributor

thalesmg commented May 3, 2024

Hi @pycan-jouza , thanks for your report. This bug shall be fixed when we release 5.7.0.

@thalesmg thalesmg closed this as completed May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants