Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

REST API for commit hook fails with 401: not authorized

Brady Vidovic June 12, 2014

I followed this guide to create a curl command to trigger a scan of my respository:

I have verified multiple times that my API key is correct. I've also noticed that I get the same response when the repository name is changed from "sso" to something that doesn't exist.

I have a single repository named "sso" in my fisheye server.

curl -X POST -H "X-Api-Key: [my key was here]"  http://fisheye1/rest-service-fecru/admin/repositories-v1/sso/scan
{"code":"401","message":"You must be an administrator to access this resource.","stacktrace":null}

1 answer

1 accepted

0 votes
Answer accepted
Brady Vidovic June 12, 2014

I ended up adding another header

-H "Content-Type: application/json"

ANd it started working. I think the documentation needs to be updated because it doesn't specify this.

lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 12, 2014

Hi Brady,

I've updated the docs to mention needing to add the content type.

Thanks,

Łukasz

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events