support http (security) headers in opamp supervisor

[cforce]

Component(s)

No response

Is your feature request related to a problem? Please describe.

Please add support for standard and custom security headers in opamp supervisor configuration.

Describe the solution you'd like

server:
  endpoint: wss://localhost:4320/v1/opamp
  headers:
    Authorization: key value
    x: 123445
    y:  hello
         

Especially it would be beneficial if authorization based on opneid connect is supported like its done fpr exporters by otel collector via extension https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/8f6fc8f16a628e0c4d6bdfd4f516ddb46b899e0c/extension/oidcauthextension

extensions:
  oidc:
    issuer_url: http://localhost:8080/auth/realms/opentelemetry
    issuer_ca_path: /etc/pki/tls/cert.pem
    audience: account
    username_claim: email

server:
  endpoint: wss://localhost:4320/v1/opamp
  auth:
    authenticator: oidc

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for cmd/opampsupervisor: @evan-bradley @atoulme @tigrannajaryan. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[srikanthccv]

Headers support will be added as a part of this PR #30237

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• cmd/opampsupervisor: @evan-bradley @atoulme @tigrannajaryan

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[cforce]

@srikanthccv Can we close this?

[srikanthccv]

Yes, the server config supports headers now.

[evan-bradley]

Closing as resolved via #30237

[cforce]

@srikanthccv @evan-bradley
This issue was rquesting as well support for openid

As far as i understood only below is now supported

server:
  endpoint: wss://localhost:4320/v1/opamp
  headers:
    Authorization: key value
    x: 123445
    y:  hello

but still below openid is not, is it?

extensions:
  oidc:
    issuer_url: http://localhost:8080/auth/realms/opentelemetry
    issuer_ca_path: /etc/pki/tls/cert.pem
    audience: account
    username_claim: email

server:
  endpoint: wss://localhost:4320/v1/opamp
  auth:
    authenticator: oidc

Can we reopen or do you want me to create an additional request?

[srikanthccv]

Please create a separate issue because the supporting auth extension is independent work.

[cforce]

Ok . see #33590