Kibana version: Newest version available
Elasticsearch version: Newest version available
APM Server version: Newest version available
APM Agent language and version: RumJS
Browser version: N/A
Original install method (e.g. download page, yum, deb, from source, etc.) and version: Fleet integration
Fresh install or upgraded from other version?: Fresh install
Is there anything special in your setup?
- Using Fleet integration to host the APM server
 - All requests are rerouted through SSL by our ingress
 
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
- When adding RumJS to our Next.js
 
application, we keep getting an authentication error regarding a secret_token.
- RumJS should not expose the secret token, so it is unclear why this error is appearing.
 - Our APM server works fine, but whenever we add RumJS to Next.js, it requests a 
secret_tokenorapi_keywhich we cannot provide. 
Steps to reproduce:
- Add RumJS to the Next.js application.
 - Configure the APM server with Fleet integration.
 - Observe the authentication error regarding 
secret_token. 
Errors in browser console (if relevant):
- Authentication error regarding 
secret_token. 
Provide logs and/or server output (if relevant):
- N/A
 
---
eck-elasticsearch:
  enabled: true
  # Name of the Elasticsearch instance.
  #
  fullnameOverride: elasticsearch
  nodeSets:
  - name: default
    count: 3
    podTemplate:
      spec:
        # This init container ensures that the max_map_count setting has been applied before starting Elasticsearch.
        # This is not required, but is encouraged when using the previous Daemonset to set max_map_count.
        # Do not use this if setting config.node.store.allow_mmap: false
        initContainers:
        - name: max-map-count-check
          command: ['sh', '-c', "while true; do mmc=$(cat /proc/sys/vm/max_map_count); if [ ${mmc} -eq 262144 ]; then exit 0; fi; sleep 1; done"]
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 50Gi
eck-kibana:
  enabled: true
  # Name of the Kibana instance.
  #
  fullnameOverride: kibana
  spec:
    # Reference to ECK-managed Elasticsearch instance, ideally from {{ "elasticsearch.fullname" }}
    #
    elasticsearchRef:
      name: elasticsearch
    config:
      # Note that these are specific to the namespace into which this example is installed, and are
      # using `elastic-stack` as configured here and detailed in the README when installing:
      #
      # `helm install es-kb-quickstart elastic/eck-stack -n elastic-stack`
      #
      # If installed outside of the `elastic-stack` namespace, the following 2 lines need modification.
      xpack.fleet.agents.elasticsearch.hosts: ["https://elasticsearch-es-http.elastic-stack.svc:9200"]
      xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-agent-http.elastic-stack.svc:8220"]
      xpack.fleet.packages:
      - name: system
        version: latest
      - name: elastic_agent
        version: latest
      - name: fleet_server
        version: latest
      - name: kubernetes
        version: latest
      - name: apm
        version: latest
      xpack.fleet.agentPolicies:
      - name: Fleet Server on ECK policy
        id: eck-fleet-server
        namespace: default
        monitoring_enabled:
        - logs
        - metrics
        package_policies:
        - name: fleet_server-1
          id: fleet_server-1
          package:
            name: fleet_server
      - name: Elastic Agent on ECK policy
        id: eck-agent
        namespace: default
        monitoring_enabled:
        - logs
        - metrics
        unenroll_timeout: 900
        package_policies:
        - package:
            name: system
          name: system-1
        - package:
            name: kubernetes
          name: kubernetes-1
eck-agent:
  enabled: true
  spec:
    # Agent policy to be used.
    policyID: eck-agent
    # Reference to ECK-managed Kibana instance.
    #
    kibanaRef:
      name: kibana
    elasticsearchRefs: []
    # Reference to ECK-managed Fleet instance.
    #
    fleetServerRef:
      name: fleet-server
    mode: fleet
    daemonSet:
      podTemplate:
        spec:
          serviceAccountName: elastic-agent
          hostNetwork: true
          dnsPolicy: ClusterFirstWithHostNet
          automountServiceAccountToken: true
          securityContext:
            runAsUser: 0
eck-fleet-server:
  enabled: true
  fullnameOverride: "fleet-server"
  spec:
    # Agent policy to be used.
    policyID: eck-fleet-server
    kibanaRef:
      name: kibana
    elasticsearchRefs:
    - name: elasticsearch
eck-apm-server:
  enabled: true
  # Count of APM Server replicas to create.
  #
  count: 1
  # Reference to ECK-managed Elasticsearch resource.
  #
  elasticsearchRef:
    name: elasticsearch
  kibanaRef:
    name: kibana
  http:
    service:
      spec:
        ports:
        - name: http
          port: 8200
          targetPort: 8200
            