You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
When configuring OpenTelemetry config in the application to send traces to Elastic, Authorization header works only for below scenarios
Hardcoded text containing 'ApiKey <APM_Auth_Token>'
<opentelemetry:headers> <opentelemetry:header key="Authorization" value="ApiKey **********" /> </opentelemetry:headers>
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.The text was updated successfully, but these errors were encountered: