To use the REST-API, you (the "API user") need to be authenticated.
https://developer.atlassian.com/display/JIRADEV/JIRA+REST+API+Example+-+Basic+Authentication
If you are not using a separate "API user" that never logs in into JIRA, but a user who logs in into JIRA, keep in mind that it might happen that during manual login, you enter a wrong password a couple of times, which - if configured this way - will lead to a situation where the API user does not work any longer because JIRA expects the user entering the captcha text or blocks the user!
Permissions
Depending on which operations you want to use via the REST services, your API user needs respective permissions in JIRA and ictime. The following permissions are required for icbiz (for all projects) if all features are used:
| Permissions | System | Description |
|---|---|---|
| Administer Projects Ability to administer a project in JIRA. | JIRA | Required to create/copy projects. |
| Browse Projects Ability to browse projects and the issues within them. | JIRA | Required to create/copy projects. |
| Create Issues Ability to create issues. | JIRA | Required to create/copy projects. |
| Create Attachments Users with this permission may create attachments. | JIRA | |
| Delete Own Attachments Users with this permission may delete own attachments. | JIRA | |
| Activity Types Permission to configure activity types | ictime | |
| Work Log Attributes Permission to manage Work Log Attributes | ictime | |
| Project Configuration Permission to configure projects | ictime | |
| Reporting Permission to generate reports | ictime | |
| Accounting Permission to charge work logs and to access accounting, including the permission to create, edit and delete work logs for projects in status inactive; also requires reporting permission | ictime |
More JIRA permissions are required if you are working with the JIRA REST API for additional operations on issues.