Custom Endpoint to Jira wierd issue 403 error

[serge calderara]

Dear all,

I have define a custom endpoint in script runner to be called from an external application

The custom enpoint is defined as below :

UpdateStatus2(httpMethod: "POST",groups:["sg-app-rlx-atlassian-adm"]) { MultivaluedMap queryParams, String body ->

CommentManager commentManager = ComponentAccessor.getCommentManager()
IssueManager issueManager = ComponentAccessor.getIssueManager()
JsonSlurper jsonSlurper = new JsonSlurper()

String JobStatusValue = jsonSlurper.parseText(body).JobStatus
//String JobIdValue=jsonSlurper.parseText(body).JobId
//String RunBookNameValue=jsonSlurper.parseText(body).RunBookName

def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser)
def searchService = ComponentAccessor.getComponent(SearchService)

// edit this query to suit
//def query = jqlQueryParser.parseQuery("project = 'Technical Service Desk' AND issuetype = 'Flush AEM Internal Cache' AND 'Azure Automation Job Id' ~ " + JobIdValue)
def query = jqlQueryParser.parseQuery("project = 'Technical Service Desk' AND issuetype = 'Flush AEM Internal Cache' AND status='In Progress'")
def search = searchService.search(user, query, PagerFilter.getUnlimitedFilter())

//search.results.each { documentIssue ->
//log.debug(documentIssue.key)
Issue issue =issueManager.getIssueObject(search.results.first().key)
// Issue issue =issueManager.getIssueObject(documentIssue.key)
commentManager.create(issue, issue.getAssignee(), "Job status has change to $JobStatusValue",true)
//}


return Response.ok().build()
}

What is happening is that if hit the endpoint from PostMan by using corresponding user/passw for Basic Auth on the request, then it is working fine without trouble.

When I ask my customer to hit the same Enpoint using same user/password for Basic Authentication, then he receive a 403 error

Any idea what is  wrong and why external user cannot hit the endpoint using postman without error?

regards

[Martin Bayer _MoroSystems_ s_r_o__]

Hi @serge calderara , it must be wrong request sent by your customer. I would check his request and compare it with your request. Can you share your postman and your customer's postmand screenshots?

[serge calderara]

hello @Martin Bayer _MoroSystems_ s_r_o__ , I have configure myself the postman request at customer site remotely so I am 100% sure it is the same.

The only difference between is the network infrastructure only 

[Martin Bayer _MoroSystems_ s_r_o__]

I am not networking expert but maybe some network device in a chain is changing headers in outcomming http request? Can you check with them?

And did yo use postman or dofferent client at customer site?

[serge calderara]

we solve it, it was due to cookies

[Manasa Nallareddy]

Hi @serge calderara ,

We are also facing the same issue can you please help us that how did you solve the issue.

[Manasa Nallareddy]

Hi @serge calderara ,

Please help us with the solution