# Trace info not available since we moved behind gateway to let keycloak oauth2 work

**URL:** <https://discuss.elastic.co/t/trace-info-not-available-since-we-moved-behind-gateway-to-let-keycloak-oauth2-work/317040>\
**Category:** APM\
**Tags:** docker, java\
**Created:** [October 19, 2022, 5:42pm UTC](https://discuss.elastic.co/t/trace-info-not-available-since-we-moved-behind-gateway-to-let-keycloak-oauth2-work/317040 "2022-10-19T17:42:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vetm73](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vetm73/32/112289_2.png) [@vetm73](https://discuss.elastic.co/u/vetm73)\
**Post date:** [October 19, 2022, 5:42pm UTC](https://discuss.elastic.co/t/trace-info-not-available-since-we-moved-behind-gateway-to-let-keycloak-oauth2-work/317040/1 "2022-10-19T17:42:37Z")

</div>

**Kibana version** :  
7.16.2  
**Elasticsearch version** :  
7.16.2  
**APM Server version** :  
1.34.1  
**APM Agent language and version** :  
Java 1.34.1  
**Browser version** :  
Latest Chrome  
**Original install method (e.g. download page, yum, deb, from source, etc.) and version**:  
Docker  
**Fresh install or upgraded from other version?**

**Is there anything special in your setup?** For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.

We run our back and frontend behind a YARP proxy that will forward automatically to keycloak and add JWT's to backend calls

**Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**:  
Before this setup (so no gateway/oauth) our APM/APM java agent setup was able to give use detailed tracing information. When changing to this setup I still find the transactions in APM but not the linked trace information.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/0/e03021a5115be0784ac467b966117d857ceac051.png)

instead of

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/6/261163b85b63cf58a48de0434928980e6b370c51.png)

**Steps to reproduce** :  
1.Both installations use the same APM configurations  
2.When moving back to old situation the trace logging is back  
3.

**Errors in browser console (if relevant)**:  
No errors

**Provide logs and/or server output (if relevant)**:

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 9, 2022, 1:43pm UTC](https://discuss.elastic.co/t/trace-info-not-available-since-we-moved-behind-gateway-to-let-keycloak-oauth2-work/317040/2 "2022-11-09T13:43:25Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.
