-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.0.8
-
None
-
6
-
On the Issue Navigator page https://jira.atlassian.com/issues/?jql= are three login links, which are not using the parameter link.login.url from seraph-config.xml. As a result, if you are using a SSO system and you changed the login urls in seraph, it won't reflect on the issue navigator page and users cannot login.
LoginUtils.js
/**
* Returns url to redirect to the current page (eg /login.jsp?os_destination=[encodedCurrentUrl]
* @returns login url
*/
redirectUrlToCurrent: function() {
var url = this.currentContextRelativePath();
return contextPath + '/login.jsp?os_destination=' + encodeURIComponent(url)
},
/**
* Returns url to redirect to (eg /login.jsp?os_destination=[encodedUrl]
* @param url url to redirect to after user has logged in
* @returns login url
*/
redirectUrl: function(url) {
return contextPath + '/login.jsp?os_destination=' + encodeURIComponent(url)
}
The main login button in the upper right corner, correctly reads the value from seraph-config.xml, but gets overwritten later by javascript.
- duplicates
-
-
- Closed
-
-
-
- Gathering Impact
-