nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Review integration with crucible not working

DIBS Drift

We're having trouble with the integration between our Jira issues and reviews in crucible

We have created Application links between the products with no errors - the "source" tab also works, but the reviews tab under a issue results in a error in crucible: crucible/var/log/atlassian-fisheye-<date.log>:

2013-05-17 12:06:55,606 WARN  [btpool0-491 ] com.atlassian.security.auth.trustedapps.filter.TrustedApplicationFilterAuthenticator TrustedApplicationFilterAuthenticator-authenticate - Failed to login trusted application: jira:10699348 due to bad URL signature.
2013-05-17 12:06:55,606 ERROR [btpool0-491 ] com.atlassian.fisheye.trustedapplications.FisheyeAuthenticationListener FisheyeAuthenticationListener-authenticationError - Error handling trusted applications authentication attempt:BAD_SIGNATURE;      Bad signature for URL: {0};     ["https://crucible.company.com/rest-service-fe/search-v1/crossRepositoryQuery?query=ISSUE-3658&amp;amp;expand=changesets[-100:-1]"]

We have tried various combinations of Trusted Application and OAuth mecanisms without luck

We have also entered "127.0.0.1" and the machines local ip in trusted IP Patterns

Thank you

Accepted answers

Foong

According to the error, there is some problem with your current settings. Try deleting and re-creating the Application Link (Trusted Application only) without any configuration for IP/URL patterns.

All comments

DIBS Drift

Versions:

Jira: v5.2.10

Crucible+fisheye: v2.10.4

Foong

According to the error, there is some problem with your current settings. Try deleting and re-creating the Application Link (Trusted Application only) without any configuration for IP/URL patterns.

DIBS Drift

We have tried that a couple of times, both with only Trusted Application and OAuth seperatly and theses two together.

I have a case active in your support system also

Foong

From the support case, we found out that FishEye has proxy settings in config.xml which is redirecting the request and causing the bad URL signature.

Removing the proxy settings and create the Application Link through localhost fix the problem.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

application-link

fisheye-crucible

review