Issue Summary

Trusted Application authentication failure logs only display internal application ID without human-readable application name, making troubleshooting difficult for administrators.

Steps to Reproduce

1. Configure Application Links between Jira instances using Trusted Applications
2. Generate authentication failures (e.g., through URL signature mismatches, clock skew, or proxy configuration issues)
3. Check the application logs for trusted application authentication failures

Expected Results

Log messages should include both the internal application ID and a human-readable identifier (application name, URL, or hostname) to help administrators quickly identify which specific application/instance is failing authentication.

Actual Results

2025-05-25 20:58:02,760-0700 https-jsse-nio-8443-exec-10 url: /login.jsp WARN anonymous 1258x974892x2 - 10.11.170.152 /login.jsp [c.a.s.a.trustedapps.filter.TrustedApplicationFilterAuthenticator] Failed to login trusted application [jira:13600974] due to bad URL signature. Received protocol version [2]. Required protocol version [2]

Administrators cannot easily identify which application corresponds to ID "jira:13600974" without running database queries or manually checking system information on multiple instances.

Workaround

Currently there is no known workaround for this behavior. Administrators must manually correlate application IDs by checking the jira.trustedapp.uid property in System Info of suspected instances or by running database queries against the propertyentry table. A workaround will be added here when available.