Jira Core behind Webseal . Can´t remove permissions

Frank Broeer July 13, 2016

Our Jira Core  (7.1.6) is behind a IBM Tivoli Webseal proxy.

 Webseal junction is unauthenticated. So everyone is able to access the Jira Application. You have to authenticate on the Jira Server

Works fine so far.

 

But in some areas there are problems.

 

e.g.

Remove permission from Permission Scheme is not possible

 

Issues  >> Permissions Schemes   Select Schema  (e.g. Test123) >> Browse Projects >> Remove

 

Error Messagge: We weren't able to complete your last action It could be for a variety of reasons, like a network or application error. You could try again, or refresh the page and try again.

 

 

 

Accessing the Jira application directly without the webseal works fine

 

 

The DELETE request doesn´t doesn´t reach the JIRA server when accessing throug the webseal, although DELETE,POST, PUT .. are allowed methods

 

This is the request without the Webseal.

1.2.3.4 - - [13/Jul/2016:11:37:18 +0200] "DELETE /rest/internal/2/managedpermissionscheme/10404 HTTP/1.1" 200 1461 "https://jira.xyz.com/secure/admin/EditPermissions!default.jspa?schemeId=10404" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36" 1081 2241

 

 

Anyone else using JIRA behind a Webseal

 

2 answers

0 votes
Frank Broeer August 10, 2016

Found the reason.

 

The JIRA DELETE Request has a body with "content"

JIRA is sending something like  „{"grantsToDelete":[11911]}“

in the body.

But Webseal expects a content length of 0  

 

There is a similiar problem mentioned in this ticket with IIS

 

https://jira.atlassian.com/browse/JRA-44424

 

 

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 13, 2016

I've run into it a couple of times, and in both cases, the answer was that the Webseal server was mishandling requests.  At a glance, it looked like it was configured correctly, but a look at the logs showed it was doing the wrong things.  I think you've got the same issue from what you've said - you need an expert on Webseal to find out and fix the settings that are interfering with the requests going to the JIRA server (I certainly needed help from a Webseal consultant.  Even off the shelf, it's a poor product for configuring)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events