Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to setup IIS 10 Reverse Proxy between self hosted Jira servers and cloud applications

Alfredo Lagrosa February 26, 2019

Can you help us configure our (Windows Server 2016) IIS 10 reverse proxy to work with our cloud applications to connect to my self hosted Jira servers through https?

Specifically, we are trying setup an application link for Smartsheet for Jira v7.9.2.

The Smartsheet for Jira application is receiving the following error message when trying to connect:

OAuth signature rejected. The public key may not match the value in JIRA or your reverse proxy settings may be incorrect. Please verify that the Public Key in your JIRA Application Link matches the value in your Smartsheet for JIRA Host listing. Also see the following guide for proxy troubleshooting actions: https://confluence.atlassian.com/display/APPLINKS/OAuth+troubleshooting+guide#OAuthtroubleshootingguide-OAuthsignaturerejected

We have followed all available online documentation, but, we can not get past the error message above.

On our IIS 10 reverse proxy server, the URL Rewrite inbound rule rewrites pattern's matching (.*) to https://myjira/{R:1}

Allowed Server Variables:
ORIGINAL_HOST local

The URL Rewrite outbound rule has two preconditions:

"IsHTML"
Using: Regular Expressions
Logical grouping: Match All
Input: {RESPONSE_CONTENT_TYPE},
Check if input string: Matches the Pattern,
Pattern: ^text/html
checked box: Ignore case

Match
Matching Scope: Response
Match the Content within: A
Content: Matches the Pattern
Using: Wildcards
Pattern: https://myjira/*
checked box: Ignore case

And "IsRedirection" with
Using: Regular Expressions
Logical grouping: Match All
Input: {RESPONSE_STATUS},
Check if input string: Matches the Pattern,
Pattern: 3\d\d
checked box: Ignore case

The Outbound rule is where the reverse proxy seems to fail.

For the Precondtion "IsHTML"
Matching scope: Response
Match the content within: A
Content: Matches the pattern
Using: Wildcards
Pattern: https://myjira/*


Action
Action type: Rewrite
Action properties: https://publicjira.mycompany.com/{R:1}
checked box: Stop processing of subsequent rules


Smartsheet support says their error log indicates the response they are receiving, https://myjira, is not the name as our public facing url, https://publicjira.mycompany.com. Thus, the connection fails.

Thank You!

AL

1 answer

Suggest an answer

Log in or Sign up to answer