Page tree
Skip to end of metadata
Go to start of metadata

Status

FunctionalityStable, maintenance stopped
Support statusDEPRECATED, unsupported
Support provided byN/A
OriginIdentity Connector Framework (Sun)
Target systemsAtlassian Jira server

Maintenance of this connector was stopped. Support for this connector may be provided if there is enough financial incentive to resume the maintenance.

Description

 JIRA Connector is REST connector for execution basic CRUD operations for accounts, projects and groups and operations related to group or projects membership. Connector uses API version 2 and was implemented for JIRA server 7.2.7.


Protocol

JIRA API

Framework

ConnId 1.4.2.14

Bundle name

com.evolveum.polygon.connector.jira.rest

Connector name

JIRA REST Connector

Capabilities and Features


Provisioning

YES


Live Synchronization

NO


Password

YES


Activation

NO

Not implemented because activation requires plugin Extender for JIRA.

Paging support

YES

Just for Account Object Type.

Native attribute names

YES

Except for Administrators.users, Administrators.groups, Developers.users, Developers.groups, binaryAvatar

Scripting

NO



Licensing

The connector itself is available under the terms of Apache License 2.0. To our best knowledge there is no extra license needed to use this connector.

Versions


Version

Origin

Binary

Samples

Sources

Build Date

Framework version

Description

1.0Polygon

GitHubN/A
Only for push and get profile avatar picture with resizing - Deprecated
2.0 PolygonDownload jar GitHubGitHubSeptember 12th 20171.4.2.14Stable version

Limitation

Connector operates with some limitations, which were detected during implementation:

  • username cannot contain characters '<', '>' or '&'.
  • email address cannot contain any special characters (except for '-', '_').
  • project keys must start with an uppercase letter, followed by one or more uppercase alphanumeric characters.
  • groups and projects do not support paging (API v2 supports just option for maximum number of returned groups.

  • when creating groups response does not provide UID (connector uses groupname as UID).

  • user activation is provided only when Extender for JIRA plugin is  installed.

Filters

Connector supports following filters and filter


EQUALSCONTAINSSTARTSWITHCONTAINSALLVALUES
Account Objectsname, UIDall attributesall attributes-
Group Objectname, UIDname--
Project ObjectsUID

all attributes
except lead

-

Administrators.users

Administrators.groups

Developers.users

Developers.groups

  • Starts With Filter for Accounts uses just username as the query parameter but JIRA API filters values of all attributes. Contains Filter works same as Starts With Filter.
  • Contains Filter and Contains All Value Filters for Projects operate thanks to all obtained values filtering on connector side (all projects or all actors) 

Configuration

Connector configuration requires three property fields, which are mandatory:

  • baseUrl - connecting to JIRA server (structure: <ip_address>:<port>)
  • username, password - authentication

Tests

JIRA Connector involves package of test classes. Tests are divided into classes:

  • according to ObjectTypes for basic and negative testing,
  • for performance tests,
  • and for configuration validity and connection tests.

Basic tests use attributes with values containing valid special characters (subset of 'ľščťžýáíéäúôöüß$#@%^&*<>(?' ) for create, update operation tests and schema consistency test. Filtering and listing tests are divided into methods according to possible filters and options for each object type.

Tests implementation expects that users, groups and projects with the same or similar attribute values as used in tests do not exist in JIRA environment. 

Configuration properties are written into static variables of JiraTestHelper class. All the test classes contains cleanUp methods for reverting state of JIRA environment into initial state after test failure and thrown exception. CleanUp methods are called within connector initialization test initTest in each test class separately for each Object type. 

  • No labels