-
Suggestion
-
Resolution: Fixed
The jiraissues macro should get it's authentication info from somewhere other than the URL in markup; e.g., a username and password could be stored in a server side configuration file, or in the database. Either would be preferable to putting the password in clear text in the markup.
- is blocked by
-
CONFSERVER-9951 Integrate Seraph's trusted applications infrastructure
- Closed
- is duplicated by
-
CONFSERVER-1595 Better authentication method for jiraissues and jiraportlet macros
- Closed
-
CONFSERVER-3729 robust (and safer) {jiraissues} macro authentication
- Closed
-
CONFSERVER-4023 Use {jiraissues} macro w/o full login info
- Closed
-
CONFSERVER-5563 Eliminate need to provide User Credentials when Adding a Jira Portlet or retrieving Jira Issues in Confluence
- Closed
- is related to
-
CONFSERVER-2478 Remote authorisation for shared users between Confluence and JIRA
- Closed