Accessing Jira Through F5 BIG-IP Access Policy Manager as a Portal Access Resource

Steve Lyons July 10, 2021

I am looking for support configuring Jira Datacenter to be proxied by F5.  Jira is configured as a webtop portal access resource.  I am unable to log into Jira through the BIG-IP if I leave the secure switch to true on the connector but can log in successfully when changing to false.

However, even when logging in I am experiencing additional issues.  One being the error "Jira is reporting that it is using the URL scheme 'http', which does not match the scheme used to run these diagnostics, 'https'. This is known to cause Jira to construct URLs using an incorrect hostname, which will result in errors in the dashboard, among other issues."  It seems no matter what changes I make within the connector or the portal access resource, this error remains.

In addition, my portal access resource is rewriting much of the data correctly accept when selecting the dashboard.  I have configured an irule to rewrite all uri's that may get missed or failed with APM but still there are objects that are not rewritten to traverse the portal access resource.  

On-prem connector

<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>

 

BIG-IP connector

<Connector port="8081" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" redirectPort="443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="false" scheme="https"
proxyName="demo.itc.demo" proxyPort="443"/>

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events