[
https://issues.apache.org/jira/browse/CONNECTORS-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688038#comment-13688038
]
Karl Wright commented on CONNECTORS-723:
----------------------------------------
bq. so i guess it would be one job per security persona (or group) and those
could have forced metadata which pushes in the ID of "who" got it.
The documentation you linked to hints that there is a concept of security level
that limits who can see a given issue:
{code}
Example
{
"self": "http://localhost:8090/jira/rest/api/2/securitylevel/10021";,
"id": "10000",
"description": "Only the reporter and internal staff can see this issue.",
"name": "Reporter Only"
}
{code}
So there is clearly a security model of some kind.
Obviously the crawling user should be able to see everything, but somehow we
need to be able to map every document into a set of access tokens, which are
matched with access tokens provided on a per-user basis by an authority service
we'd also need to write. There was a similar discussion pertaining to
Confluence - see
http://www.mail-archive.com/[email protected]/msg00715.html . I
wonder if they have similar models?
> Jira Connector
> --------------
>
> Key: CONNECTORS-723
> URL: https://issues.apache.org/jira/browse/CONNECTORS-723
> Project: ManifoldCF
> Issue Type: Improvement
> Components: JIRA connector
> Affects Versions: ManifoldCF 1.3
> Reporter: Andrew Janowczyk
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.3
>
> Attachments: jira-connector-for-manifold.patch
>
>
> Why not Jira Connector? :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
