# RUM injection requires basic authentication?

**URL:** <https://community.dynatrace.com/t/rum-injection-requires-basic-authentication/40206>\
**Category:** Dynatrace Managed\
**Tags:** real-user-monitoring-classic, dynatrace-managed, javascript\
**Created:** [June 14, 2023, 12:23pm UTC](https://community.dynatrace.com/t/rum-injection-requires-basic-authentication/40206 "2023-06-14T12:23:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![josef\_solnicky](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/josef_solnicky/32/31968_2.png) [@josef\_solnicky](https://community.dynatrace.com/u/josef_solnicky)\
**Post date:** [June 14, 2023, 12:23pm UTC](https://community.dynatrace.com/t/rum-injection-requires-basic-authentication/40206/1 "2023-06-14T12:23:59Z")

</div>

Hi,

we have one case where basic authentication popup window appeared - just after fullstack Dynatrace monitoring was enabled. We identified one of Tomcat processes as source - when we disabled RUM injection - application started to behave correctly.  
When we tried to tag user session via dtrum.identifyUser – the dtrum was not found, even we see ruxitagentjs in HTML as first script. Looks no data is coming back to Dynatrace.

Where should we continue with investigation?

BR, Josef

---

<div class="post-metadata">

**Author:** ![radek\_jasinski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radek_jasinski/32/10432_2.png) [@radek\_jasinski](https://community.dynatrace.com/u/radek_jasinski)\
**Post date:** [June 14, 2023, 1:15pm UTC](https://community.dynatrace.com/t/rum-injection-requires-basic-authentication/40206/2 "2023-06-14T13:15:54Z")

</div>

Hi,

Please check that you have your network connection open and that you don’t have blocked requests: [Infrastructure pass-through requirements for RUM Classic — Dynatrace Docs](https://www.dynatrace.com/support/help/shortlink/rum-firewall#requests)

The second issue is the proper placement of JS in the source of your page.

 ![rumverification-1185-e2fac60638.png](https://global.discourse-cdn.com/dynatrace/original/3X/3/e/3ea673719a0b5779810d801872dac44a50f7e72b.png)

Regards,

Radek

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [June 14, 2023, 2:05pm UTC](https://community.dynatrace.com/t/rum-injection-requires-basic-authentication/40206/3 "2023-06-14T14:05:42Z")

</div>

[@josef\_solnicky](https://community.dynatrace.com/user/9567)&nbsp;, The ruxit js may be placed somewhere with no proper permissions in your app… Check the suggestion by [@radek\_jasinski](https://community.dynatrace.com/user/16832) , to change the default JS placement and issue should be resolved.

I faced this same behavior with my clients, mostly when they apps are exposed to users by a proxy, and app running on WAS. Changing the JS default context/path resolved the issue.
