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

Support for Authorization header to accept expression with encrypted token and text #90

Open
dileepkumarvinayagam opened this issue Dec 1, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@dileepkumarvinayagam
Copy link

dileepkumarvinayagam commented Dec 1, 2022

When configuring OpenTelemetry config in the application to send traces to Elastic, Authorization header works only for below scenarios

  1. Hardcoded text containing 'ApiKey <APM_Auth_Token>' <opentelemetry:headers> <opentelemetry:header key="Authorization" value="ApiKey **********" /> </opentelemetry:headers>

  2. Encrypting text - 'ApiKey <APM_Auth_Token>' and accessing it as secured property <opentelemetry:headers> <opentelemetry:header key="Authorization" value="${secure::elastic.apm.authToken}" /> </opentelemetry:headers>

And, it doesn't work when encrypting only Auth_token and passing 'ApiKey' and secured token in the value expression for Authorization header - <opentelemetry:headers> <opentelemetry:header key="Authorization" value="#['ApiKey ' ++p('secure::elastic.apm.authToken')]" /> </opentelemetry:headers> . In this scenario, OpenTelemetry doesn't raise any errors and also there's no trace sent to Elastic.

@manikmagar manikmagar added the bug Something isn't working label Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants