Azure-docs: JIRA Azure Active Directory integration: We receive "Invalid response. Empty Destination value. Please contact your Azure AD admin."

Created on 1 Mar 2018  Â·  16Comments  Â·  Source: MicrosoftDocs/azure-docs

Everything looks good on both AD and JIRA, however we recieve "Invalid response. Empty Destination value. Please contact your Azure AD admin." when logging in. It brings us to login with Azure AD, then after providing a PW it bring us back to JIRA with the above message. Any ideas? Seems someone else had an issue but it was lost with this new feedback system, no idea if anyone found a solution. We're using a newer JIRA which is the only thing I can think of (v7.8) Thanks!


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

  • ID: d38cad90-6574-38c2-3262-059a9f975064
  • Version Independent ID: dd08d5c5-65a4-c2cc-8b51-7a35268dde68
  • Content
  • Content Source
  • Service: active-directory
Pri2 active-directorsvc assigned-to-author product-question triaged

Most helpful comment

@leemac and @aazizi18 We found the issue and fixed it for the 7.8 version. Now we are publishing the newer version of the plugin in the Microsoft Download center. Once the update is complete then I will update this thread. Current planned ETA is Monday EOD.

All 16 comments

@MarkusVi FYI...

@jeevansd Could you have a look at this ?

@Adam-Smith-MSFT Yes, I am looking into this issue.

@leemac Yes today our plugin support JIRA 6.0 - 7.2 But we are testing JIRA 7.8 which is the latest version. Provide us some time and we will come up with the solution. In the mean time can you please reach back to us on this email address [email protected] and we will schedule the call with you to resolve your issue.

Wow you guys are fast. Will do tomorrow! A call could work some time next week (monday?), would love to get this working for our team and I'm sure other's will appreciate as they upgrade. I'll reach out in the morning (EST).

Hey @leemac @jeevansd
have you guys found a solution for this issue ... i have Jira 7.8 and having the same issue .

Thanks in Advance .

@leemac and @aazizi18 We found the issue and fixed it for the 7.8 version. Now we are publishing the newer version of the plugin in the Microsoft Download center. Once the update is complete then I will update this thread. Current planned ETA is Monday EOD.

I also encountered with the exact issue described above. it would be helpful to get the new version of the plugin ASAP.
Thanks!

@leemac @arixon1 and @aazizi18 we have now uploaded the new version of the plugin here.
http://download.microsoft.com/download/3/C/9/3C94C886-0C89-4182-A758-6DB982E1F398/MicrosoftJIRASSO6x7x.obr
Please use this new plugin and try. Let us know how it goes.

Thank you @jeevansd! It appears to work now.

I did have to walk through the tutorial again. After I uploaded the plugin to jira, I go the same error, perhaps something was cached or had to be reapplied. Everything looks good now on our end.

@leemac Thanks for the confirmation and we are really happy to help you up!
@arixon1 and @aazizi18 Can you please confirm the output? Is the issue resolved for you?

Hi, I can confirm that it is working now, thank you.
However, we have a situation that our Jira server resides on our local LAN (on-prem) and we would like to publish it externally through Azure application proxy. since Application Proxy cannot work with SAML the SSO only works internally. how can we overcome this issue?

Thanks!

@arixon1 Thanks for the confirmation.
If you want to use this app from outside of your organization you will need application proxy along with this Microsoft JIRA gallery app. You need to create an Application Proxy app say app1 where the internal URL is the JIRA SP initiated Sign on URL. So this way the users can invoke this app and can initiate SSO. Then you need App Proxy app say App2 which has the internal URL as JIRA Reply URL (ACS URL) this way the SAML token can come in.
Then you need to modify the SAML JIRA app to post the token/Reply URL to App 2 external URL. This way Azure AD can post the token to the App2 and then App2 will bring that token to the internal endpoint. You might have to change the option of App 2 which says Translate Headers to "No"

Note that in this case you are telling users to use the Access Panel which is https://myapps.microsoft.com and click on App1 which will do everything for them.

Give it a try and let me know how that goes.

--Jeevan Desarda

@jeevansd
Thank You ! it worked !!!

@aazizi18 Great. Thanks for the confirmation.
@Adam-Smith-MSFT Can you please close this issue?

@leemac We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JeffLoo-ong picture JeffLoo-ong  Â·  3Comments

paulmarshall picture paulmarshall  Â·  3Comments

Ponant picture Ponant  Â·  3Comments

jebeld17 picture jebeld17  Â·  3Comments

behnam89 picture behnam89  Â·  3Comments