# \#authentication **URL:** https://community.dynatrace.com/tag/authentication/741.md [Latest](https://community.dynatrace.com/latest.md) · [Categories](https://community.dynatrace.com/categories.md) · [Tags](https://community.dynatrace.com/tags.md) --- ## [Dynatrace MCP OAuth refresh fails after logout—supported approach for persistent per-user access?](https://community.dynatrace.com/t/dynatrace-mcp-oauth-refresh-fails-after-logout-supported-approach-for-persistent-per-user-access/57117)
**Author:** [@vedant05422](https://community.dynatrace.com/u/vedant05422)\ **Replies:** 4\ **Last updated:** [October 21, 2026, 2:30am UTC](https://community.dynatrace.com/t/dynatrace-mcp-oauth-refresh-fails-after-logout-supported-approach-for-persistent-per-user-access/57117 "2026-10-21T02:30:37Z")
We’re connecting Rhythms to Dynatrace’s hosted remote MCP server using a confidential OAuth client with Authorization Code + PKCE. We need reliable per-user access without requiring users to remain signed into Dynatrace …