Calling Custom REST API Calls on Crucible 2.10.0 when integrated with crowd

Karanam Subbarao
Contributor
March 19, 2013

We have developed some custom REST API which make calls to Crucible/Fisheye

In Previous versions 2.8.1 we use to call REST as follows

1. Get /rest-service/auth-v1/login call and retrieve token

2. Call the REST API through Jersey webResource.header("Cookie", "remember=" + token) and it used to work

3. But now we have done integration of crucible with crowd with custom crowd token key .

When I pass the crowd token key it works.

if I dont pass the crowd token key it fails...

Did something change in 2.10.0

1 answer

0 votes
Matthias Cullmann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 17, 2013

I noticed some changes too. With 2.8 I could call repositoryAdminService.create in my anonymous REST API implementation, in 2.10 I get:

com.atlassian.crucible.spi.services.NotPermittedException: You are not authorized to perform this operation

at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.ensureAdminPermission(DefaultRepositoryAdminService.java:1269)

What changed and how are we supposed to get AdminPermissions?

Regards

Matthias

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events