Customers need the ability to access the Jira UI directly via https://ip:port (using the server’s IP address and port) even when Jira’s configured base URL uses a different hostname (e.g., FQDN with proxyName). This is currently blocked by strict XSRF (Cross-Site Request Forgery) checks and authentication logic introduced in Jira 10.2.x and later.
Their security policy requires all access to be over SSL (no plain HTTP), and customer cannot open additional non-SSL ports.