-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Current jiraissues macro supports Jira instances with public access and allows including statically defined user credentials into the Jira URL for restricted access Jiras.
I propose the following intermediate Jira / Confluence integration improvement into the macro:
1) Add a new "Trusted Jira addresses" preference into the Administration section which would allow the admin to list a set of trusted jira instances (ie, beginnings of the URL).
2) Enhance jiraissues so that if the Jira which is being linked to with the macro is in the list of trusted Jiras, the osuser=xxx&ospassword=yyy is automatically appended into the url, with the credentials of the current user.
The above enhancement combined with configuring Confluence to use Jira's user database would allow for much more extensive use of the macro as then the user credentials would be safe and users would only see the issues they have access to.
- duplicates
-
CONFSERVER-2711 Better authentication method for jiraissues and jiraportlet macros
- Closed
- is incorporated by
-
CONFSERVER-796 JIRA integration
- Closed
- is related to
-
CONFSERVER-2952 JIRA and Confluence Single Sign-On
- Closed
-
CWD-523 The Confluence JIRA Issue macro currently uses the hard coded os_username and os_password properties for authentication, it would be nice to use the authenticated user in the browser.
- Closed